Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
elktown
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
181.
▲
by
elktown
2y ago
> but he seems to want the best for everyone This kind of indefinite benefit of the doubt is just class solidarity within the upper middle class.
182.
▲
by
elktown
2y ago
Not sure how the entire npm/react/SPA ecosystem can be described as stable when it's so many moving parts that it's almost a running joke. Latest I've seen is going full circle into the server-side again and some ki
183.
▲
by
elktown
2y ago
> Large companies typically have dedicated frontend teams with designers to build a user experience that feels cohesive across their products, so managing different specializations and the communication overhead is already part of their
184.
▲
by
elktown
2y ago
Sure. But the field looked a lot different in 2000 than today, and the weight of each of these have shifted vastly along with different hypes, trends, the introduction of cloud providers etc. Microservices in particular is often decided at
185.
▲
by
elktown
2y ago
I wonder how this translates to today's microservice craze that is more of a infra/devops/org decision that leaks into the software design in various imo detrimental ways. I can certainly see scenarios where merging microserv
186.
▲
by
elktown
2y ago
So what makes sense to you is adding the additional layer of transforming the JSON data into HTML from an API - all of which are almost always in the end tailor made for the app anyway - using a significant chunk of code within a completely
187.
▲
by
elktown
2y ago
> the backend serves data, the client renders it SSR does this as well. The server serves data (HTML), the client (web browser) renders it.
188.
▲
by
elktown
2y ago
I'm curious to know if you avoid movies/TV-shows in a similar manner?
189.
▲
by
elktown
2y ago
> The options are basically US-aligned dictator, or USSR-aligned dictator. It's a textbook example of it, just like this follow up. But I expect nothing else from a user that for years and years always, with no exceptions, no matte
190.
▲
by
elktown
2y ago
Yes, constructing a justification through surgically extracted shallow gotchas (but ofc told in an authoritative way like any good gaslighter would do) in each case and ignoring the general pattern - it doesn't exactly end at 3 occurre
191.
▲
by
elktown
2y ago
False dichotomy
192.
▲
by
elktown
2y ago
It's both worrying and refreshing that reactionaries of today are comfortable enough to just say "Yeah, so what if we did?" instead of the usual weaseling.
193.
▲
by
elktown
2y ago
> Nobody is endorsing the practices in TFA “because it’s Google”/in order to be like Google. Sure, people elsewhere make those claims all the time, and they’re wrong, but that’s not in evidence here that I can see. I disagree, I thi
194.
▲
by
elktown
2y ago
> On the other hand, the book has some nuggets that make it worth reading Definitely! Mostly just a word of caution to not get overeager hoping to apply this everywhere, because "here be dragons".
195.
▲
by
elktown
2y ago
"If you are only one developer" suggests zero interests in being nuanced. To be clear, this linked specifically to simplicity which I'm certainly in favor of emphasizing the importance of. But IME the exact opposite happens w
196.
▲
by
elktown
2y ago
Just remember that what google writes in these kind of things is not universal. It's written from their very unusual circumstances. You can certainly pick nuggets that are more universal than others but, like in many other instances, t
197.
▲
by
elktown
2y ago
Could be indeed. I've also found it interesting how rarely I hear about actual proper load testing. Like, it doesn't need to be a horrible experience, and it can be done in a controlled setting before even launching if one wants t
198.
▲
by
elktown
2y ago
The amount of assumptions involved in all these really suggests it's mostly rationalization doesn't it? It's absolutely perfectly fine to scale to millions of users with yesterday's proven simple tech using the benefits
199.
▲
by
elktown
2y ago
Not sure if there's any other profession than software that has such a hard time with proportionality. We can seemingly with a perfectly straight face argue that yes this massive Rube Goldberg machine was required to avoid that small n
200.
▲
by
elktown
2y ago
It's also an excellent way to create large organizations due to the complexity chain reaction it seems to kick off.
201.
▲
by
elktown
2y ago
The only reason "AGI" is around the corner is because people with vested interests - emotional, profit etc - are going to redefine it to suit their purposes. We've already seen this with AI which is now just any bog standard
202.
▲
by
elktown
3y ago
> people are losing their jobs at a rapid rate now due to AI No, they aren't. > Is he deluded, as you put it? I don't know what each for your apostles has said. But anyone who claims that with just a hyped up LLM behind them
203.
▲
by
elktown
3y ago
> The reason why coding pays so well is because it's IQ-gated in a way that plumbing isn't. Pretty rich by someone with a comment history littered with AI delusions: > AI will largely replace software developers very soon, a
204.
▲
by
elktown
3y ago
No one changed VMs manually over SSH beyond perhaps deep debugging. Yes, creating a VM image might be needed, it might not, depending on approach [1]. Most of those things you listed are primarily an issue after you've already dug a ho
205.
▲
by
elktown
3y ago
> if you have a small org with one CRUD app on a handful of VMs I think most would be surprised how big chunk of modern apps are within that space without active intervention by stuff like microservices. No need to stop at a handful of V
206.
▲
by
elktown
3y ago
> The most severe, prevalent danger is people thinking these things are too complex and then trying to roll their own alternative on bare VMs No it's not. This was simply just not the case before k8s. Running a stateless app behind
207.
▲
by
elktown
3y ago
Not sure what kind of apps this is but I can't see the big value-add on a golang app binary wrt to being cloud agnostic, nor wrt local development. It makes even less assumptions on the user's env. Still need some cloud conf (terr
208.
▲
by
elktown
3y ago
Something feels very off and mantra-like with the proportionality of how often cloud migration benefits are being presented as something very important to how often that actually happens in practice. Not to even mention that it also assumes
209.
▲
by
elktown
3y ago
Alright, just feels like taking a bit too far into the exceptions. Even back then only large companies would consider that. Renting servers, renting a server rack (co-location), or even just a in-office server rack for what would be a start
210.
▲
by
elktown
3y ago
Not sure how how you could jump all the way to running your own Asian datacenter from my post. A bit amusing though :). I even wrote that it's worth running the LB/DB in the Cloud?
More ›