hota_mazi

7 ms·

31.
by hota_mazi 3y ago
Go gives you the illusion of simplicity because it gets rid of guard rails and error checking. If you remove all error checking, of course your code is going to look a lot simpler. It's also going to be a lot more wrong and crashy. Wai
32.
by hota_mazi 3y ago
I was a big Amiga fan back then, and I think for a long time, it was a superior machine to pretty much anything else (preemptive multitasking, multi chips, great graphics and sound, etc...). In 1995, I booted Windows 95 for the first time a
33.
by hota_mazi 3y ago
> I haven't actively used Windows since 2008. It's such an obnoxious OS to use You might want to modernize your perception of it, holding on to 15 year old views is not a very smart move in the tech industry. Windows 10 and 11
34.
by hota_mazi 3y ago
You probably live in the US and parent lives... anywhere else in the world really.
35.
by hota_mazi 3y ago
Yup, that's POP CS, 0x0f. Since it made no sense to use, it became the way 286 and later processors used to indicate multibyte opcodes. When a 286 is running the code, encountering a 0x0f means that the following opcode is multibyte, w
36.
by hota_mazi 3y ago
Checked exceptions failed because developers are lazy and don't want to check for errors. Checked exceptions force you to do more work, but it's essential work to make your code more robust. Replacing them with runtime exceptions
37.
by hota_mazi 3y ago
Given the barrage of negative comments on the PR and here as well, it really feels like Andrew is the only person in favor of that change. It's his language, obviously, but I strongly suspect that if this PR goes through, it will compl
38.
by hota_mazi 3y ago
> Everyone just started using unchecked exceptions because they provide an easier coding experience. Yes, in much the same way that no longer checking for error codes provides an easier coding experience. But it makes your code more cras
39.
by hota_mazi 3y ago
Everyone who uses Clojure, and even people who don't, but know Lisp, understand the point: since parentheses are used in Lisp to delineate everything , it makes sense to use a different pair of symbols to make parameter lists stand ou
40.
by hota_mazi 3y ago
I disagree. As opposed to most compiler articles, this one actually covers code generation for every section of its chapters, which is really great. I also like that every chapter focuses on a specific feature and describes how to implement
41.
by hota_mazi 3y ago
And yet, Clojure, the most used Lisp today, decided to use brackets instead of parentheses for parameter lists, breaking with 50 years of Lisp tradition. How dare they?? But I'm sure you know better than them.
42.
by hota_mazi 3y ago
Slavery was widely confirmed for even longer. Tradition, right? How about instead of using tradition to decide if something is beneficial or not, you just assess it on its value?
43.
by hota_mazi 3y ago
> Because it's a 50-year old convention That's a terrible reason to justify... well, anything, really.
44.
by hota_mazi 3y ago
While the barebones aspect of Lisp is appealing, there is no way I will commit again to a language that's not statically typed. There is a difference for a language between "readable" and "understandable". To me, la
45.
by hota_mazi 3y ago
I've actually gone one step further and I'm pretty sure I can adapt to anything now. I coded in Java for 20+ years and then switched to Kotlin. Semicolons were gone, it was a breath of fresh air. And then I learned Rust and I face
46.
by hota_mazi 3y ago
Sure, but playing a game you haven't bought is clearly illegal, there is no grey area there.
47.
by hota_mazi 3y ago
Playing a game you haven't bought is illegal, there is no grey area here.
48.
by hota_mazi 3y ago
My thought exactly. The freedom of individuals clearly stops at illegal acts.
49.
by hota_mazi 3y ago
Couldn't it be argued that it's totally okay to have two separate meanings for "to comprise" as a direct verb (A comprises B), and mean the opposite when used in indirect form (B is comprised of A)?
50.
by hota_mazi 3y ago
I know La/TeX is the standard for this but I'm still irritated that it forces all diagrams to appear at the top of the page, which really gets in the way of explaining things clearly. This books suffers a lot from this limitation,
51.
by hota_mazi 3y ago
> Hence, we provide a proof of P = NP. Is this serious?
52.
by hota_mazi 4y ago
Indeed. And it's not hard to find screenshots of the actual game since Space Invaders is a very popular project for people interested in emulation: https://github.com/cbeust/space-invade.rs
53.
by hota_mazi 4y ago
Plenty more floundered because of that shortsightedness. Surely you realize that picking one of the most successful apps created this past decade is not the resounding endorsement you think it is.
54.
by hota_mazi 4y ago
> void popFront() => ++index; So in D, `popFront()` not only returns... nothing (void) but then returns... an index? No wonder nobody uses this language.
55.
by hota_mazi 4y ago
> Properties help avoid this anti-pattern by making it possible to transparently swap in a computed property for what used to be a plain field. Java's getters and setters *are* properties. Just with more syntactic sugar than languag
56.
by hota_mazi 4y ago
> Java does indeed represent an anti-pattern of verbose and frequently trivial getters and setters. It's not an anti-pattern. This is how Java provides the exact functionality that you describe as very important (field encapsulation
57.
by hota_mazi 4y ago
If you think today's Microsoft is anything like the Microsoft of 20 years ago, you need to start reading up on tech news other than Slashdot.
58.
by hota_mazi 4y ago
Or you forming an opinion 30 years ago and never changing it. Textbook definition of "closed minded".
59.
by hota_mazi 4y ago
This is 2023 and you are saying that Microsoft is less ethical than Oracle. A lot of things have happened since the 90s, you know?
60.
by hota_mazi 4y ago
> For me, "begin" and "end" are actually much more comfortable to type, Type, maybe, but they are visual noise when you read code. BEGIN and END are also not as easy to match with editors/IDE's as pairs of s

More ›