ttfkam

13 ms·

91.
by ttfkam 2y ago
The fact that you have to go to often heroic measures to keep your bundle size under 500KB even for simple apps doesn't make it irrelevant or useless. It is indeed bloated: on the development boilerplate side, the bundling/deploym
92.
by ttfkam 2y ago
Depends on your goals/focus: Smaller, cleaner, and faster code while still focusing on dynamic interfaces? Svelte or SolidJS Focus on server-side HTML rendering with little to no browser dynamism? PHP (It really is quite nice now.) Foc
93.
by ttfkam 2y ago
I like Svelte too, but take another look at Angular. Your memories of Angular 9 don't match up anymore. It's A LOT more streamlined now with so much less boilerplate than before. And signals. That said, transitioning to some backe
94.
by ttfkam 2y ago
I'm still laughing about the fact that JSX renders to XHTML, not the HTML5 that browsers actually use. 99% of the time they're the same and parsing occurs as expected. That last 1%, things get weird quick.
95.
by ttfkam 2y ago
No accounting for taste, I suppose. For me, class components were absolutely horrid and hooks simply made it less horrid by comparison. I guess anything can seem amazing after you've been stuck in knee-deep mud.
96.
by ttfkam 2y ago
Studies have shown that number of lines of code is directly proportional to the number of bugs produced in that code, regardless of language or framework. Would it stand to reason then that a framework (yes, I said it) like React with its b
97.
by ttfkam 2y ago
Putin gets more boots on the ground and could potentially lessen the number of dead Russians to explain back home. Kim has more than enough boots to spare and gets a steady supply of resources for his resource-starved country, eg. food and
98.
by ttfkam 2y ago
Easy enough to figure out he's not one of the three enumerated dissenters, but the article curiously omits Roberts from the list of concurring justices.
99.
by ttfkam 2y ago
2021
100.
by ttfkam 2y ago
Should be marked 2021. The current release version is 16 with 17 now in beta.
101.
by ttfkam 2y ago
I love how all the responses are talking about these arcane footguns that require watching obscure talks to be aware of. Then there's the other segment of C++ programmers talking about how modern C++ is so much better now to the point
102.
by ttfkam 2y ago
Excess deaths were noticed long before the vaccines were available, which largely rules out the vaccines as the smoking gun the headline suggests. (Paywalled.) Excess deaths could have come from stress, isolation, poor eating habits, limite
103.
by ttfkam 2y ago
None of those are automatic. Any API you write still has to remember to put in LIMIT clauses, to avoid OFFSET. And then you have to actually write the API rather than have it generated for you. There are no free lunches, especially with reg
104.
by ttfkam 2y ago
Ceci n'est pas un message.
105.
by ttfkam 2y ago
Unit testing row-level security policies is far from the hardest thing to test/debug. Not sure what this guy is talking about.
106.
by ttfkam 2y ago
Hasura and Postgraphile are quite performant. No complaints there. And you can both put queries on an allow list, control max query depth, and/or throttle on query cost.
107.
by ttfkam 2y ago
Not particularly scary. For something like Hasura, resolvers are opt-in, not opt-out. So that should alleviate some of your concerns off the bat. For Postgraphile, it leans more heavily on the database, which I prefer. Set up some row-level
108.
by ttfkam 2y ago
The only time I think GraphQL works is when it is when the GraphQL schema and resolvers are autogenerated by the underlying data stores. As a ORM layer, I love solutions like Postgraphile and Hasura where they mostly just reflect the struct
109.
by ttfkam 2y ago
Someday… someday… (sub)urban dwellers will wake up to cars being the problem, not the type of car. Yep, EVs are better than ICEs. Public transportation and proper infrastructure is far better (and cheaper overall). Get the public transit in
110.
Tesla Blames User for Crushed Finger(businessinsider.com)
8 points by ttfkam 2y ago|2 comments
111.
by ttfkam 2y ago
Have a nice day. https://benchmarksgame-team.pages.debian.net/benchmarksgame/... And that $1.53/hr is per instance. $13,402.80/yr per instance. Now calculate 100 instances. 200. 1,000. Now find a CFO or CTO w
112.
by ttfkam 2y ago
Feel free to compare against C. :)
113.
by ttfkam 2y ago
https://xkcd.com/2347/
114.
by ttfkam 2y ago
Except when 10s of thousands of requests can be handled in 32GB of RAM versus in Java where you need an instance four times as big to handle a load one fourth the size. That's annoying when you only need one or two instances. A real de
115.
by ttfkam 2y ago
Been coding in Java since the late 1990s with v1.0.2 and continue to this day with v21. Java has been and remains a comparative memory hog. Yes, it is still popular, but it is far less popular than it used to be for greenfield projects. Go:
116.
by ttfkam 2y ago
Yup, fixing CVEs is job security!
117.
by ttfkam 2y ago
Several orders of magnitude more RAM used by Java as well for the same amount of work.
118.
by ttfkam 2y ago
SQL once again the GenX of languages, keeping foundational aspects working reliably while being mostly ignored as other technologies constantly seek attention and pats on the back. "Bad programmers worry about the code. Good programmer
119.
by ttfkam 2y ago
Pretty sure John D. Rockefeller talked politics. William Randolph Hearst had his own newspaper and gave rise to the term "yellow journalism". Henry Ford was a fascist, complete with glowing admiration for Hitler. Wealthy individua
120.
by ttfkam 2y ago
You forgot to mention (Web)Workers. This is explicit creation, management, and communication with additional threads within JavaScript. What's more, they've been around in JavaScript longer than the V8 engine has even existed! ht

More ›