i share some of this sentiment as well and i think a lot of my hesitance is that these solutions seem born of the popularity of rust. we have had c and c++ for as long as javascript has been a full-stack workhorse. is it just the barrier of entry / novelty of rust has prompted longtime js devs to make the leap into building tooling? along with it, it seems the "new framework every week" jab at javascript can be applied to the build system as well. in any case, i welcome the speed improvements and this certainly does not preclude me from using these new tools where i'm able.
Readit Newszcmack commented on Skeptical of rewriting JavaScript tools in "faster" languages nolanlawson.com/2024/10/2... · Posted by u/todsacerdoti
zcmack commented on Keep your phone number private with Signal usernames signal.org/blog/phone-num... · Posted by u/Josely
Yeah, nah, it might be fashionable but I'm not 100% convinced that it's not an operation intended to be a lightening rod for "private" communication.
Given how tightly they control development, disallow third-party clients, disallow federation, disallow self-hosting servers, have a history if disallowing use without google play and have hid huge development features from the public (mobile-coin) despite being open source. etc;
The idea that it's a great undertaking of our time is so bombastic that it's guaranteed to be false even if you truly believe that they are completely altruistic (which I'm willing to believe but it's not coming easy to me based on the above).
"What's better"? Matrix. Which seeks to solve all of my points, the only thing lacking is market share which honestly is partially caused by these "easy to use" services which trade off everything else, which also consumes developer mind-share even if you're unwilling to acknowledge that. (devs are motivated to solve issues for friends, family and themselves if they are exposed more frequently to systems and services that are sub-par).
in a world where iOS users won't install another free app from the app store because they already use iMessage, matrix is like asking for your friends to perform calculus just to talk to you.
zcmack commented on Htmx, Rust and Shuttle: A New Rapid Prototyping Stack shuttle.rs/blog/2023/10/2... · Posted by u/openquery
this seems like great for rapid prototyping for those that are already well-versed in rust and really really hate javascript.
zcmack commented on My journey away from the JAMstack spicyweb.dev/farewell-jam... · Posted by u/brycewray
I think this person is trying to say they moved from Netlify to Render, with some moderately insane, vague anecdotes, like:
> Things which used to take hours or days to accomplish in standard Rails or Laravel or Django apps—most of this stuff isn’t rocket science, folks—now took weeks or months! Progress!
This article is too much of a narrative to be coherent about issues with Netlify + the Jamstack... and also too verbose of a narrative to be readable. I'd skip it, but maybe you'll find it entertaining.
i completely agree. use the right tool for the job. if you need significantly dynamic content, you should consider another framework such as rails (as the author indicates).
if netlify is being portrayed as the only platform to deploy a statically generated site from git commit, then i suppose yes, the sane defaults of these frameworks are not the right tool _for you_.
zcmack commented on Ask HN: Is the market bad, or am I having the worst luck job hunting? · Posted by u/imadkhan
This would be funny if it wasn't so sad.
When people started asking these questions, the whole point was to see how people reason about a new problem they haven't solved before. There are almost no work problems that require you to regurgitate something verbatim you saw on leetcode before.
It's seriously making me question the intelligence of these interviewers. Although at the same time I realize it's mainly just to arbitrarily whittle down the applicant pool to a smaller number you can interview in person.
it is very sad. i personally would much rather someone walks through their problem solving approach and identifies shortcomings/edge cases than to regurgitate a memorized algorithm.
it's really easy to identify code that is not optimal at code review time. it is far more challenging to have a conversation with a algorithm-regurgitating robot that their entire approach was wrong because they misunderstood the abstraction or that their code wasn't needed because Larry is refactoring that part of the system to a separate service already.
zcmack commented on Brave Browser introduces vertical tabs brave.com/vertical-tabs/... · Posted by u/czottmann
close your damn tabs, heathens
zcmack commented on Conventional wisdom as an anti-pattern bower.sh/anti-pattern... · Posted by u/qudat
I've written so many automated tests, but how many have actually caught something important? A couple dozen?
Yeah I'm glad TDD isn't the dominant religion any more. If you write a test and it never fails throughout the lifetime of the project, thats wasted time.
i think TDD is a great method, but not dogma. likewise with code coverage. being prescriptive about one or the other just leads to angry people who get fed up with the principle and rebel.
don't know much about fly.io, but i would have definitely deployed my go binary + caddy w/config in a container, rather than setup a systemd service on the host. just me?
zcmack commented on GitHub staff are required to use Teams by Sep 1, 2023 twitter.com/karrisaarinen... · Posted by u/gslin
act like its so bad, they've been using ruby since inception.
haven't we already been doing this since email templating was a thing?