nesarkvechnep

The whole article feels like a rationalisation for vibe coding your product from now on.

This is my mentality but when it comes to my company. I want to have clients for which I consistently produce solid work, no flash, no news headlines. Doing the work and quietly building a reputation.

Unfortunately, it made me even more sad because the project I'm working on now is complete trash. Every line outdoes the previous in the dumbest thing possible. Four years at the company and not a single greenfield project for me, only well established piles of... you get the idea.

After school I played countless hours of Euro Truck Simulator. It was an awesome escapism. Being a truck driver, driving through sun and snow, in different parts of Europe. Crazy drivers at night, needed to think quick in difficult situations.

Did Linus Torvalds convince you, with his history of outbursts, that Linux is done?

In what way the article convinced you that Andrew Kelley is not professional enough for a serious project like Zig? Isn't his contribution to the language what's important?

See SGML for a markup language.

It’s a problem of philosophy, not tooling.

This is exactly what happens in a typical Elixir project even though Ecto is a query builder and not an ORM. People define their domain entities as database tables. The result is, from my latest project, you have user and organisation memberships which are a list of membership records. This is carried throughout the application while it should be a hash map of organisation IDs and membership data, so you can check if a user is a member of an organisation in constant time. Of course keeping ourselves coupled to the database representation is easier than defining a view, for example, which takes care of presenting the data in a useful form for the application.

Development of Zig feels so wholesome.

Did they die?

Just yesterday I was thinking about the BEAM and would it be tidier if it were written in Zig.

Yeah, but you must know about them and the possible bug first in order to allow them...

This is just HTTP. The definitive guide to REST is "Architectural Styles and the Design of Network-based Software Architectures" by Roy Fielding.

Obviously, yes, but is it simpler to add a new HTTP method and add support for it everywhere?

I still don't get the need for QUERY. One can create a search or filter resource with a POST request and then query it using GET. As a bonus, creating a resource allows it to be shared and cached.

There's no such thing as REST spec. The closes mechanism to actual REST is to create a resource using POST and then query it using GET. You have the added benefit of the resource being cacheable.

It's probably what they know so not anything new should be learned.

Ah, sorry, it wasn't /dev/udp but socat - echo "hello" | socat - UNIX-SENDTO:/path/to/socket.

I find /dev/udp much more useful. I can create aliases for fire and forget commands to my daemons without actually writing *ctl program.

I did the same but with Nix.

Thank you for the clarification. I guess authors these days assume they don't need to state the Unix flavour they're talking about.

More related to OMamas.

As a student I used to work as a network administrator in the summer breaks. The place had a very nice library of technical books. I had the pleasure to read "Database Design for Mere Mortals" there, in the hours when work was slow.

The disagreement is on Ecto schemas used to represent databases tables from the persistence layer to the UI. Of course, use changesets to normalise user input but using the same schemas everywhere is a sign of immaturity as a developer. You really sound like someone who only does CRUD services. Real world is often more complex.

Yeah, one of the worst practices. I've been working with Elixir professionally for 6 years now and I still see this sh*t everywhere. Bad APIs, bad UIs because someone coupled themselves to the database structure and can't escape. List of memberships? Keep them as a list with the same fields as the junction table. Top-level APIs taking maps with string keys as "params" so they can very easily be cast for a changeset.

Not at all. It’s used to build standard web applications too.

Why not Erlang?

It's is great in everything which requires talking to and/or listening on a socket. It's amazing for writing and running daemons.

I did the same integration with an Erlang daemon. All relevant key presses are sent to it and based on the current focused application the daemon does different things. I built an Erlang library i3_IPC to listen for events and send commands to Sway.

Thank you for the lecture but I didn’t mean that. I meant `Either String String` is possible in Haskell and not in C# because… C# is strongly-typed.