HN user

cianuro_

54 karma
Posts0
Comments26
View on HN
No posts found.

They dominate the premium market.

Tim Cook, as CEO of a public company, is incentivized to deliver shareholder value.

Entering this market with a good product does just that.

Beyond that, this is an entry point for people to use Apple products. It can be bridge to get this consumer to buy more premium hardware and software later on.

I use Elixir every day with Claude Code and I haven’t had any issue regarding syntax, ecosystem and BEAM specific knowledge yet.

If anything I perceive a bit more mistakes when I have to do things in TS (and in a way simpler domain, in a way smaller project).

A game in Love2D. Using Fennel instead of Lua. It is a humbling experience coming from web dev.

Heavily using Claude Code to build my own kanban and a Cloudflare native headless CMS meant to feed Astro websites.

To me this is another sign the written word is dead.

With so many mechanisms for creating users and posting en masse, I find it really hard to believe the contents of any comment or post I read that goes past a paragraph or two. And of course I am still skeptical even if it is less than 2 paragraphs of text.

I find the contents of that specific post hard to believe. Specially since the user hasn't participated in the conversation at all.

I like this place a lot and it saddens me we are just going to see more of this.

It is OK to separate yourself from a group when you deeply disagree with their actions, no matter how insignificant it might seem to a different group of people.

However, I am glad this happened. New Linux Ambassadors will step up and this issue will be buried into the alternative social media communities such as Mastodon, never to be heard of again.

I disagree that Framework will lose a meaningful amount of business over this.

There is value in fast iteration and delivery. These are early stage startups, the clock is ticking. I wouldn’t do it with JS but I understand why it would be used.

Now we can argue how good or bad the nodejs (or any alternative JS implementation) is. At the end of the day the objective is most likely to rock the boat enough to be acquired and have a payday. With enough discipline you can get far before the footguns show up.

Can you map the BEAM features against the zoo of options you mentioned so readers understand what exactly are these other options and how they compare to BEAM?

Zod v4 Beta 1 year ago

Yes, I agree. Some sort of check has to happen somewhere to validate the incoming payload. If you’re looking for type safety, it makes sense to use Zod for this.

To me it is bending the original tool (JS, async driven, weak typing) to fit a purpose it was not made for (hard typing, synchronous) in detriment of what it is that makes the tool good in the first place (IO performance).

Zod v4 Beta 1 year ago

I completely understand TypeScript, Zod not so much. The context here is performance.

My understanding is that Zod performs synchronous operations to validate the schemas. Something about "using the tool correctly" resonates here. Maybe don’t validate very large and nested schemas frequently and things like that.

But I can’t help but think it is adding another layer of potential footguns that you have to be mindful about. Maybe the benefits outshine the risks in disciplined teams that understand both the tool and the runtime. However I can’t help but think about the less disciplined teams abusing Zod and then wondering why things are slow.

I have not yet fallen out of love for computing. Recently I had a "microsecond" moment where I thought "this is bullshit".

I have recently came back to the topic of software engineering always "having" to keep up.

At the end of the day what keeps me going is the creative opportunity (specifically trimming out the block and carving out a statue) and the fact that this is the closest I will ever be to be a wizard.

IME, the productivity promise falls short. I have found major gains following an integrated framework over multiple code bases with the same language.

With the setup you described I just felt I had to write more, even if it was in the same language.

Finding good devs is hard on its own, but you have to consider the market you are looking at.

NextJS/React covers a massive talent pool, so you will inevitably get less experienced candidates going through your pipeline until a good one shows up.

You might not spend as much time if you were tapping into the markets of say Clojure or Elixir, maybe even Go. Not telling you to change your stack, just highlighting the differences in talent pool size and quality.

Be transparent with the compensation from the get go. If you are trying to tap LATAM markets, good devs are reaching (close to, but still a bit far) US salaries, so offering 70-80k for a Senior role won’t guarantee a Senior dev.

Why re release my 2008 game as a remaster in 2023 if Sven in Sweden already patched the (open) source with QOL changes and provided higher texture mods.

It does cut on future dumb re releases :)

Not from the Netherlands but from a small third world country: farmers around here like to buy things on spot doing handshake deals and carrying bags of cash. I've heard them buying a lot things from cattle to agricultural supplies and even vehicles.

Mind you, this is a poor country. The middle class in the capital city can't even dream of making what these farmers make.

This was my path, too. I performed exceedingly well and did the hardest things nobody raised their hand to do. This was also a startup where I had been for a while. The added company specific context and industry specific context helped.

But really, I am not staff. I do not intend to sell myself as one, yet.

[dead] 5 years ago

Are you able to provide a source for that statement? All I could find were theoretical procedures that have not been performed.