And it is fine! This website uses table for layout, so...

Hacker News "webmaster" stopped in 90's.

And it is better that way!

It is easier for the frontend developer to look only to the status code of the response and pop up a paywall or something, rather than some message in the boby. The same goes for 401 Unauthorized or 403 Forbidden, etc.

I am skeptical with what people is calling 'AI' this days. I was expecting to see the generated code before subscription, there is a lot of sass that clain they have AI, but is only a bunch of if's and people 'helping the code'

I see your point. And I also understand your skepticism. You're not the first and don't expect you to be the last :) Trying to sum why we are calling AI to our product:

- Our model learned the website's components visually (e.g. what is a navbar, an input, a button, etc) - The AI outputs the UI elements' coordinates - Without the output from our deep learning model we aren't able to automate the whole process

Regarding examples of the generated code, as said previously, it's definitely on our top priorities.

You're being overly harsh. Sometimes there's also an else.

Or even an if else.

Nice! I am only missing a way to move a pile of cards.

That's actually something I've already tested out, so probably coming soon! Hit test + long-press-and-drag should do it!

These ads are not intrusive. You can read the article perfectly. They are not obstructing your experience. You, however, is consuming their content and blocking their advertisers...

Adblocking is the first line of defense against malware and invasive online tracking.

(By adblocking I don't mean like AdBlock Plus I mean more like uBlock Origin.)

Also, that page gave me dizziness. Why that background colors? Jesus!

-"MacOs is too closed! Apple lock the user" (Now you can install kernel extensions) -"It's insecure!

> (Now you can install kernel extensions)

This is wrong. There is no "now." Kernel extensions have been installable in macOS since 10.0, IIRC. The real "issue" here is that Apple has provided a mechanism for installing Kernel extensions into a protected bucket, but no way to uninstall them.

The fact that this whole thing isn't very well (or at all) documented even for developers (the ones writing the kernel extensions), seems like it's not the most ideal of situations.

Apple in general has always been a bit further in this direction, but it seems companies are increasingly leaning towards security over freedom, which is perhaps even more scary than insecurity itself. It's a hard position for a company to be in, but I suppose it comes from the fact that it seems receiving negative PR about being insecure is worse than PR about being unfree.

As a memorable saying goes: "The security people won't be satisified until everyone is living in prison."

When in the history of Mac OS X could you not install kexts?

Macbook Pro 13 Early 2011. Upgraded to SSD and 8Gb memory. Still works well!