Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dgb23
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
34 ms
·
541.
▲
by
dgb23
2y ago
Plus those libraries are often very hard to read and understand. Maybe I'm just dense though.
542.
▲
by
dgb23
2y ago
Apart from localization all of the things you mentioned come with Go as well. There's net/smtp, database/sql. You can implement in-memory sessions in Go with a few lines or use the well established gorilla sessions or similar
543.
▲
by
dgb23
2y ago
You can't fully replicate JSON schemas in either language without writing logic. In terms of just static definitions, Go has typed container types while PHP has not. That's a pretty common case for JSON. PHP is more convenient at
544.
▲
by
dgb23
2y ago
If you use the std lib you can write a simple web app in Go as well in few lines of code? The only difference would be a little bit of boilerplate for setting up application state (a few lines) and the necessary type definitions, which you
545.
▲
by
dgb23
2y ago
One of the major issues I have with GraphQL from the get go is that it introduces it's own syntax instead of using a commonly understood and established _data_ format like JSON or similar. Same problem with Prisma Model definitions and
546.
▲
by
dgb23
2y ago
I think the hype is mostly over because of useReducer. It's the simplest thing that lets you structure your code in the way you want if you'd had chosen Redux (or similar).
547.
▲
by
dgb23
2y ago
DRY is perhaps the most misunderstood principle in programming. It’s primarily about data normalization and decoupling information in your code. Yet people confuse it with building abstractions.
548.
▲
by
dgb23
2y ago
Expressiveness has many dimensions. It depends on what you are trying to express in the first place. C++ or Rust are expressive in both directions, towards the metal and upwards in terms of abstractions. But those languages are not easy to
549.
▲
by
dgb23
2y ago
There are degrees and different shades of "success" and "functional programming". Clojure is successful, stable and well maintained. However it is a niche language compared the big mainstream languages. It takes a functi
550.
▲
by
dgb23
2y ago
Responsibility and power should always go hand in hand or something is broken.
551.
▲
by
dgb23
2y ago
A lot of social media platforms lose money because they decide they want to grow above and beyond, even after being well established. Same thing for other software products that are perfectly fine, even loved.
552.
▲
by
dgb23
2y ago
Enshittification is not a necessary consequence for a sustainable business. But I think social media platforms are susceptible to forces that pull beyond that.
553.
▲
by
dgb23
2y ago
I like my parens in a muted color with the currently active one highlighted. Rainbow colors are extremely distracting and overloading to me.
554.
▲
by
dgb23
2y ago
They are apparently a database company though.
555.
▲
by
dgb23
2y ago
Well yes. This isn’t for everyone. The company has to pay a premium and the workers have to sacrifice time. But if you make these sorts of promises you have to make sacrifices. I think it’s refreshing to see this kind of thing though.
556.
▲
by
dgb23
2y ago
This could happen to anyone. You’re tired or thinking of something else, the attack weirdly aligns and you don’t notice it until it’s too late.
557.
▲
by
dgb23
3y ago
It’s pretty good at completing relatively simple code. If you already know what exactly you write and have a consistent and simple coding style it will typically recognize what you are doing and complete whole blocks. It takes an experience
558.
▲
by
dgb23
3y ago
This is very very sound advice. How many _actual_ data structures are there in our day to day? Trees, graphs, buffers, arrays, hashmaps, state machines... Yet we tend to overspecify operations as if they are special (see: many applications
559.
▲
by
dgb23
3y ago
Also README driven development seems similar, with a different target audience.
560.
▲
by
dgb23
3y ago
When I played around with zig, I got a much better understanding what they actually are and how they are (or can be) represented in memory. It's a language that lets you actually feel what your program is doing.
561.
▲
by
dgb23
3y ago
> this discussion will soon be futile Yes we could simply ask the AGI what to do anyways. I hope it's friendly.
562.
▲
by
dgb23
3y ago
It seems more like a self-made, systemic problem.
563.
▲
by
dgb23
3y ago
Plus, there's likely far less "random" code in the tree, due to go packages generally having fewer dependencies. It's a cultural thing, yes, but it's there in practice.
564.
▲
by
dgb23
3y ago
Doesn't that also mean it scales up the negative consequences just as much? More code = more maintenance, risk, bugs, resource usage etc. Sometimes these things are worth it because the manual process is error prone and perhaps frustra
565.
▲
by
dgb23
3y ago
This viewpoint existed (to a more extreme degree) in the 18th and 19th century too. "If we give everyone the vote then...", "If workers have protections then...", "If women had equal rights then..." etc. It
566.
▲
by
dgb23
3y ago
"Wealth is not a zero sum game" has some truth in it but is ultimately false. There's only so much inhabitable space, only so many resources and only so many people on earth. You only have so much time to live and even thinki
567.
▲
by
dgb23
3y ago
I've yet to read that book, I've heard a lot of good things about it. The above comment is referring to: https://en.wikipedia.org/wiki/Capital_in_the_Twenty-First_Ce...
568.
▲
by
dgb23
3y ago
What you describe has something to do with this: Being poor is expensive. Everyone who struggled financially at some point in their time intuitively knows how much harder it is to make (and keep) money if you're poor. Saving your first
569.
▲
by
dgb23
3y ago
Yeah, I mean stuff you can't or won't put into the client-server communication. At some level of detail it becomes wasteful. For example a multi-step form, where you can browse for options, have a lot of filters such as logic that
570.
▲
by
dgb23
3y ago
This can get hairy very fast. With every project that grew the need for UI state I either wished I went with client side rendering or did so from the start for the parts that needed it. The issue is: manipulating the DOM can become hard to
More ›