90s_dev

34 ms·

541.
by 90s_dev 1y ago
Reading through this code is a veritable rite of passage. You learn how C works, how text editors work, how VT codes work, how syntax highlighting works, how find works, and how little code it really takes to make anything when you strip
542.
by 90s_dev 1y ago
I don't even use editor suggestions for the next word I should write. For me, something I didn't think of myself is not mine.
543.
by 90s_dev 1y ago
1. What do you like about Zig more than Rust? 2. How did you ensure your Zig/C memory was freed properly? 3. What do you not like about Rust?
544.
by 90s_dev 1y ago
It's not.
545.
by 90s_dev 1y ago
The point is that it's layered. 1. Validate your Buffer/UInt8Array for valid size/encoding/etc first 2. Parse it to an object via JSON.parse or whatever your use-case needs 3. Reach into it with this function to get data
546.
by 90s_dev 1y ago
Did they cancel it because dosbox exists? If so, that's smart.
547.
by 90s_dev 1y ago
Or kilo[1] [0]: https://github.com/antirez/kilo/
548.
by 90s_dev 1y ago
I think the difference is that burnout can even be for things you're excited about and want to do, but subconsciously don't want to do for other reasons, e.g. the task/project goes against your ethics but you're push
549.
Ask HN: What are some "eureka" projects?
4 points by 90s_dev 1y ago|1 comments
550.
by 90s_dev 1y ago
> and you can even locally reason about the code much better than in typical 'unsafe' languages like C++. Do you have an example of this? I'm just a TypeScript guy who never had a fair chance to use C++ or Rust for long, s
551.
by 90s_dev 1y ago
Interesting how we always go in circles. edit.cmd was one of the first programs I ever used. Now it's back rewritten as a Windows 10+ program in Rust? Yet it looks and works just the same as 30 years ago!
552.
by 90s_dev 1y ago
I hope someone adds typed Lua support and sends a PR!
553.
by 90s_dev 1y ago
Not disdain, just skepticism. One too many experts have gravely misled me to damaging effect.
554.
by 90s_dev 1y ago
Yeah I just made it up.
555.
by 90s_dev 1y ago
On the other hand, the latest research and innovations are often gravely harmful but touted as safe and helpful for a long time by the experts, like lobotomies.
556.
by 90s_dev 1y ago
Ah so you're the guru I should have studied under all those years. If only.
557.
by 90s_dev 1y ago
I've never touched an LLM and won't use AI. Everything I ever have and will make is hand crafted.
558.
by 90s_dev 1y ago
Maybe you're right, what do I know? I don't have a PhD in this field. Just relating what I've seen in myself and others throughout my life.
559.
by 90s_dev 1y ago
I've learned from the so-called experts for years. I studied directly under them. I spent so many years trying to find the perfect way to do TDD and BDD. I saw their own code and their own solutions up close. They're frauds. It wa
560.
by 90s_dev 1y ago
Type systems make 93% of tests obsolete. The other 7% are implied by developing new features and making sure they work as you expect. If nothing broke, you're good to go. Incidentally, it scales with a team. The more people writing cod
561.
by 90s_dev 1y ago
People who think like that commenter implied, are almost always indoctrinated into "if you don't write tests and use TDD or at least BDD, you're literally Satan ."
562.
by 90s_dev 1y ago
"If I haven't seen it, it's new to me." I'm very happy to see the case being made for static typing. Dynamic types should be niche, and eventually they will be. Rails and Python only made them popular out of a react
563.
by 90s_dev 1y ago
Unless they're just flat out lying, no: > This is the result of a multiyear effort to prepare for this
564.
by 90s_dev 1y ago
> Give them time and relevant experience, and they will arrive at the same conclusions: What does this say about DHH then? He's got decades of experience yet ripped TypeScript out of his codebase angrily, preferring the foggy myster
565.
by 90s_dev 1y ago
TDD and BDD are security blankets for enterprises and clients. They add disproportionately little value, and significantly increase the cost of evolving an app in any direction.
566.
by 90s_dev 1y ago
> Now, why doesn’t bytes.Reader implement Peek? It’s just a byte slice, it’s definitely possible to peek ahead without altering stream state. But it was overlooked, and instead this workaround is applied. When I first looked at Go, it se
567.
by 90s_dev 1y ago
That's actually all it was in the beginning. Just writing code for fun. But the more code I wrote, the more it evolved into an app that demands to be released, especially since the nature of it is to be a platform, SDK, and API for ot
568.
by 90s_dev 1y ago
Array.isArray isn't needed when you know your array isn't going to be deserialized e.g. via MessagePort. What other supposed bugs? And yes I'm aware this doesn't have a huge API surface. That's the whole point. If
569.
by 90s_dev 1y ago
I'm on the fence. But the new idea would fully break compatibility, and is much better. Should I continue to indefinitely support a product I no longer believe in?
570.
by 90s_dev 1y ago
const cached = new Map<string, Function>() export function as<T>(o: any, path: string, as: (o: any) => T | undefined) { try { let fn = cached.get(path) if (!fn) cached.set(path, fn = new Function(&#x27

More ›