HNHacker News
TopNewBestAskShowJobs

hota_mazi

2,724 karma · joined May 30, 2016

submissionscomments
hota_mazi··on Game Jam 2 Results
Good habit, maybe, but it shouldn't cause a compilation failure.

Add to that the snowball effect: you comment out a variable, compile, and you get another error because commenting out variable a made variable b unused. Rinse and repeat.

It's a huge and totally unnecessary time sink.

It should be opt-in, so that it's a warning by default, and then, when I'm ready to push my code, I could run some --strict mode that would force me to clean up my code.

hota_mazi··on Apple II Desktop Updated
I stand corrected.

I remember using MUI back then, maybe it added this behavior although even now, I'm no longer sure I can trust my memory on that.

hota_mazi··on Apple II Desktop Updated
AmigaOS predates RISC OS by two years (1985 / 1987).

It was also a true preemptive multitasking OS (as you pointed out, Windows would only become preemptive with Windows 95), had the same move window behavior you describe (thanks to the Amiga's specialized chipsets, namely the Copper and the Blitter) and it also featured proportional scrollbars (another thing that would only land in Windows ten years later).

hota_mazi··on Cowgod's Chip-8 Technical Reference
Here is a Kotlin implementation of the emulator: https://github.com/cbeust/chip-8

and in particular, how each operand is implemented:

https://github.com/cbeust/chip-8/blob/master/src/main/kotlin...

hota_mazi··on 50 years Smalltalk anniversary celebration at Computer History Museum
> there are no buts and ifs, or extra products to install.

So... moving the goal posts now.

hota_mazi··on 50 years Smalltalk anniversary celebration at Computer History Museum
Yes and yes. On the JVM and .net. Has been feasible for a while.

It's also something that you should probably never do, so not really that useful or worth considering as a major advantage.

hota_mazi··on 50 years Smalltalk anniversary celebration at Computer History Museum
These IDE's have been able to do this for 20+ years.

And they also do so much more than the rrb.

hota_mazi··on Why I quit using SwiftUI
Man... I don't know what's so hard to understand. You put icons on your desktop anywhere you want all the time, don't you?

They're not all stacked up starting at the left corner, are they?

Imagine that all I want is three icons on my home screen, all lined up on the right edge of the screen, where they are easy to reach by my thumb.

You can't do that on iOS.

hota_mazi··on 50 years Smalltalk anniversary celebration at Computer History Museum
> The productivity that a handful of good smalltalkers can achieve to solve complex systems is off the charts.

You could say that of any experts in any system. They will be extremely productive.

There is really nothing special about Smalltalk that makes its developers automatically more productive (especially not the IDE, which is vastly outclassed today by the likes of IDEA, XCode, and Visual Studio).

hota_mazi··on Why I quit using SwiftUI
I don't know how else I can describe it, maybe you're so used to it you don't see how limiting it is.

Here is a thread on reddit describing it:

https://www.reddit.com/r/ios/comments/r2vs1x/why_cant_you_pu...

There are a few solutions around it, some require a jailbroken iPhone, others use empty widgets to create "fake space".

hota_mazi··on Why I quit using SwiftUI
No, not talking about overlapping.

Just talking about being able to grab an icon and position it anywhere I want on the screen (possibly snapped to a grid).

Right now, icons have to be aligned in rows anchored in the top left corner, so that whenever you insert a new one, all the ones after that get pushed right or down, messing up your entire layout.

We've had this ability on desktops since Windows 3 thirty years ago, and Android has had it since day one. As does macOS. Why not iOS?

hota_mazi··on Why I quit using SwiftUI
It's not just for cosmetic reasons, there are practical, actual benefits from a user experience standpoint.

For example, I put the apps that I use the most often on the right hand side of the screen, where my thumb can reach them faster. I can't do that on iOS (well, I can, but then any new app I put on the home screen will mess the entire arrangement and I will spend another ten minutes calculating what to insert and where to get all these icons back on the right side of the screen).

I just don't understand how Apple, a company that prides itself on great user experience, is still putting their users through this UX hell fifteen years after the release of the iPhone, and they don't seem to think it's an important feature to add.

hota_mazi··on Why I quit using SwiftUI
You cannot put an icon anywhere you want on the home screen.

Icons are lined up left to right, in a row.

You need to insert icons inside a row and then all the other icons to its right will be pushed right and/or down.

hota_mazi··on Why I quit using SwiftUI
iOS still doesn't let you place icons anywhere you want on the home screen, though. It's been fifteen years.

Desktops, and Android, have allowed you to do this for decades.

hota_mazi··on We don't know how the universe began, and we will never know
Could you outline what's problematic about it here?
hota_mazi··on We don't know how the universe began, and we will never know
Yes but why should we care what the bible says, especially when what it says contradicts science?
hota_mazi··on We don't know how the universe began, and we will never know
There are also hypotheses stating that the universe has always existed and that the Big Bang was just a phase change.

This blows away all religious arguments trying to plug a creator in there: since the universe was never created, it doesn't need a creator.

hota_mazi··on We don't know how the universe began, and we will never know
Why do you need a reason? Maybe there is no purpose. The universe just is, period.

If you look at an ant, do you ask yourself "Why is this ant here?".

hota_mazi··on We don't know how the universe began, and we will never know
There is no evidence to believe that's true, so you shouldn't believe it and assume that your current life is all you have. Enjoy it to the fullest while it lasts.
hota_mazi··on We don't know how the universe began, and we will never know
Faith is the justification that people give when they believe something for no good reason.

You can believe anything based on faith, therefore, it's not a reliable path to truth.

Only reason is.

The faster our civilization gets rid of faith, the better off we'll be.

hota_mazi··on Finnish as a world language?
Hangul is a marvel of an alphabet, especially when you realize it was created from scratch six centuries ago.
hota_mazi··on Is Haskell really the language of geniuses and academia? (2019)
You make a lot of awesome points.

The lesson I derive from Haskell is that "If it compiles, it will work"

1. is inflated nonsense

2. has a lot less to do with Haskell-the-language than with Haskell-the-type-system

I have observed a similar phenomenon with Rust. That statement is not perfect, it's hyperbole. If it compiles, it doesn't mean it will run (otherwise, why bother writing code? We just write function signatures and call it a day).

But Rust's type system is incredibly sophisticated, just like Haskell's.

And guess what... Rust supports mutability. It doesn't just support it, it encourages it. It tells you "Step over that fence, it's okay, I got your back".

It's so liberating.

The secret here is not functional programming. It's not immutability.

It's a sound and powerful type system.

hota_mazi··on Byte Magazine Special Issue: Smalltalk (1984)
That's the developer license. The price to deploy was... close to absurd.
hota_mazi··on Byte Magazine Special Issue: Smalltalk (1984)
> What makes you think Smalltalk was sold on the basis of runtime performance?

Nothing, because I never said anything of the sort.

What I did say was that Smalltalk has always been very slow compared to other languages. It was true decades ago, it's still true today.

hota_mazi··on Byte Magazine Special Issue: Smalltalk (1984)
Well, saying that it's faster than the two slowest mainstream languages today is not exactly setting the bar very high :)
hota_mazi··on Byte Magazine Special Issue: Smalltalk (1984)
Price is one of the main factors, for sure.

But it's not just that.

The image was actually a big turn off even back then, even before source control was even a thing.

Even today, Smalltalk runtimes (e.g. Pharo) are extremely slow compared to other languages, now imagine how slow Smalltalk was forty years ago... I can tell you, it was very, very slow (I used it on NeXT back then). I'm talking "watch the window draw with your naked eye" slow.

hota_mazi··on Byte Magazine: LISP (1979)
Oh absolutely! Browsing through these pages today, I find myself reading the ads a lot more than the actual articles, which haven't aged well.

But back then... man, these ads were cancer and they made up 80% of the weight and price of the magazine.

hota_mazi··on Byte Magazine: LISP (1979)
Mmmh... no.

I grew up and learned programming in that era, bought magazines, typed pages and pages of listings.

98% of the listings in these magazines were BASIC, 1% were assembly, and the rest was... well, others.

LOGO was a niche language then, and Forth even more so.

hota_mazi··on Byte Magazine: LISP (1979)
Wasn't it predictable, though?

Take a look at that issue of BYTE entirely dedicated to LOGO that was referenced multiple times in this discussion.

A dozen articles about the language, with listings. The screenshots? All the same, showing recursive pictures of rectangles and circles. Great. LOGO can do that. But what else? Big empty void there.

Contrast that with what BASIC could do at the time... Is it any wonder LOGO died out and BASIC thrived?

hota_mazi··on Byte Magazine: LISP (1979)
To be fair, out of these 256 pages, 200 are really just ads.

Your point still stands, but the actual substance is a lot smaller than you describe.

← PreviousPage 5 of 34Next →