Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
likortera
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
likortera
4y ago
I think the key on this comment is "90s". Modern PHP is very different. As you say, Laravel makes trivial and a joy to use things that in 90s PHP are like today's node.
32.
▲
by
likortera
4y ago
Most "full stack" frameworks in the node ecosystem consider themselves "full stack" just because you can run code on the server. See the Fresh (deno) discussion here in HN from a few weeks ago. To me a framework which do
33.
▲
by
likortera
4y ago
Bad. Like really bad. Unless you're doing it for some small corner case where you need up to the list bit of performance, raw SQL queries and mapping them to objects or manually moving or many pulsating the result sets manually is real
34.
▲
by
likortera
4y ago
Adonis is far, far, far from reaching even a small percent of what Laravel is. It has almost no community and very little or almost no third party packages. When I tried it las year I couldn't even find a formatter for the templates. L
35.
▲
by
likortera
4y ago
Same here, except I use Unpoly for all my side projects.
36.
▲
by
likortera
4y ago
I think you're only considering the backend part of these frameworks. Rails is really full stack. Django's frontend story is a joke.
37.
▲
by
likortera
4y ago
Yeah, that's the point. I think the SDK is not that helpful when running code in the backend (SSR). What frustrates me is that I don't get what's wrong with just using the traditional http-only secure cookie backed by a serve
38.
▲
by
likortera
4y ago
I really wish directus had a simple "cookie" based auth, and not all this crazyness with a cookie + refresh token + renewals + refresh + JWTs +... I was trying to use it with Next.js, where I needed to authenticate the current use
39.
▲
by
likortera
4y ago
Hit reload like crazy. I was desperate.
40.
▲
by
likortera
4y ago
I like react, and next. I use it at work and it pays my bills. But I 100% agree with you, the complexity is mind blowing. And I'm pretty scared of all the upcoming server components, etc... It is a very powerful tool for sure, but it i
41.
▲
by
likortera
4y ago
Ha! I've met web developers that didn't know that you could do form posts without a JSON API
42.
▲
by
likortera
4y ago
I like https://tallstack.dev/ a lot. But I think https://unpoly.com/ is nice also and works with any backend. Tailwind for CSS is great too.
43.
▲
by
likortera
4y ago
Too Javaish for my taste.
44.
▲
by
likortera
4y ago
It is very likely that GAE will last a lot more than the Kubernetes cowboy you hired to set up the undocumented and untested version of it in house.
45.
▲
by
likortera
4y ago
> I started out with Iaas namely Google App Engine and we suffered a ton with huge bills especially from our managed db instance Are you factoring in the salaries of the people setting up Kubernetes? And the cost of those people/sal
46.
▲
by
likortera
4y ago
I've only used SWR. How does it compare? I
47.
▲
by
likortera
4y ago
Yes, they do. You get these "for free" with any PaaS. You have to do it yourself with vps or custom in house kubernetes.
48.
▲
by
likortera
4y ago
Yes, because optimising for docker image size sounds like the right thing to optimize for.
49.
▲
by
likortera
4y ago
What about backups? What about the vps going down? What about upgrading the server? What about security updates? Professional work on VPS is either a lot more work, or not that professional. If it is not being a lot more work then you'
50.
▲
by
likortera
4y ago
Yes, I agree. The "minimum complexity" is way higher this way, even for simple things. But my fear is that when things get complex in the frontend, at some point there is a peak point at which these tools become easier and the mor
51.
▲
by
likortera
4y ago
Something it took me some time to understand, and I feel very dumb for that, is that with these modern "SPA" tools such as Next, you can still do quite easily dumbed down non interactive websites that do traditional form posts. It
52.
▲
by
likortera
4y ago
I don't find this anything better than just using Next.js or any similar framework. Custom solutions for bundling end up being custom reinvented square wheels in my experience.
53.
▲
by
likortera
4y ago
It's forking all the way down. I run my code on a fork of Linux, just in case.
54.
▲
by
likortera
4y ago
Problems that most of Kubernetes users don't have, and could have been solved with some unfashionable 2/3 servers and a load balancer.
55.
▲
by
likortera
4y ago
No need to go back 30 years. If doing professional work, use heroku, App Engine or any similar PaaS solution. If doing hobby/side projects, Dokku is a great self hosted heroku alternative. Easy to setup and use. Kubernetes is a very lo
56.
▲
by
likortera
4y ago
And almost impossible to understand or maintain to anyone coming after you to the project. The benefits of frameworks is that there's shared knowledge on how to use it, lots of documentation and they are more battle proven. There'
57.
▲
by
likortera
4y ago
Recommending people that don't know how to/if to do it (that's why they are asking) to write their own auth, trivializing the problem and in the same comment recommending using JWT terrifies me quite a lot.
58.
▲
by
likortera
4y ago
And I'm not sure about the cheaper.
59.
▲
by
likortera
4y ago
You push your code and only god knows where it runs but cheaper and more webscale.
60.
▲
by
likortera
4y ago
haha, lol... So I'm a top 1% dev then :). I have all the megabytes in my frontend.
More ›