Hacker Newsnew | past | comments | ask | show | jobs | submit | more blinkingled's commentslogin

I love using KDE and use it on all my desktop machines. I even have a source compiled version ready to test / hack on if I need - utterly fun and easy to build using kde-builder and works on most distros including Ubuntu/Debian, Arch and Fedora.

That said, I don't think having yet another immutable distro is a great idea if they are only going to punt and use Flatpaks. They can run flatpaks on any distro out there. So not really understanding the idea behind this. Nothing really stands out from the article - they still need to make KDE work great with most other modern versions of the distros so it isn't like Flatpaks based KDE is going to give them an edge in having the best KDE on their own distro.

What am I missing?


Thanks, that is definitely a good sign - given the rendering engine monopoly state of Chrome+derivatives and lack of great momentum behind Firefox adoption we need Apple to actively keep Safari not just viable but great even if only on macOS/iOS.


Crazy that Deno is still not workable on FreeBSD because of the Rust V8 bindings not being ported.


How big is the intersection of modern Javascript developers and FreeBSD users?


Not as big as Linux but I know a few FreeBSD shops that run NodeJS apps so it's not entirely crazy to think that there are more and they would want to try Deno. Besides making your OSS software compilable on *BSD/Linux/Mac/Win has historically been a good thing to do anyways.


For a lowlevel runtime (ie V8 itself) I can accept certain lag since there might be some low-level differences in how signals,etc behave.

However for more generic code Linux'isms often signals a certain "works-on-my-machine" mentality that might even hinder cross-distro compatibility, let alone getting things to work on Windows and/or osX development machines.

I guess a Rust binding for V8 is a tad borderline, not necessarily low-level but still an indicator that there's a lack of care for getting things to work on other machines.


Is it big enough to prioritize fixing though? The answer seems to be a no so far.


Node.js is (maybe surprisingly) used a lot in less common operating systems like FreeBSD and Illumos.


It's more than a little surprising that portability between different Unices is not given more emphasis. "Back in the day" a program being portable between Sun Solaris, HP's HP-UX, Linux, FreeBSD was considered a sign of clean code.


Back in the day, Sun Solaris and HP-UX were not end-of-life, and FreeBSD had more equal industry footing with Linux. Now Linux is the clear winner in server OS UNIX by a wide margin. Also, Ryan Dhal worked at Joyent, a Illumos/Solaris shop when he built Node; perhaps that has informed his lack of interest in supporting FreeBSD these days.


Looks like it is in ports?


Trying to compile it - it's 2.2.0 but better than nothing. I haven't seen any upstream patches for Rust V8 for FBSD so maybe out of tree ones in the ports if it does compile.


I mean... you can probably see why they don't spend any effort on that.


Try to actually use a recent version. Never had a problem with late plasma 5 and recent Plasma 6 on Arch.


Very clearly written article - didn't feel like they were trying to sell you their viewpoint - just laid down the facts concisely.


Hopefully 8Gb isn't reserved for Apple Intelligence?


It is not


Just tried asking Llama 3.2:3b to write a YAML file with Kubernetes Deployment definition. It spit the yaml out but along with a ton of explanations. But when I followed up with below it did what I want it to do.

>>> Remove the explanation parts and only leave yaml in place from above response. apiVersion: apps/v1 kind: Deployment metadata: name: my-deployment spec: replicas: 3 ...

Alternatively this worked as well >>> Write a YAML file with kubernetes deployment object in it. Response should only contain the yaml file, no explanations. ... ions. ```yml apiVersion: apps/v1 kind: Deployment metadata: name: example-deployment spec: replicas: 3 selector: matchLabels: app: example-app template: metadata: labels: app: example-app spec: containers: - name: example-container image: nginx:latest ports: - containerPort: 80 ```


If anyone has an idea how in the modern day one could run a search engine, be sustainable and provide quality results without being influenced by advertisers, SEO hacks and also maintain security around it all - infected pages etc. - they are not on HN and are probably too busy implementing their idea. Kidding aside as a thought exercise what can people think of to kind of sort of make modern search engine work?

I am asking because I get the feeling that there's not much you can do and Google's way is the only thing anyone can do and still be in business. Now how much they rely on ad revenue and how much more they have to compromise is another story. Probably Google should be thinking of including better search to paying Google One customers?

Biggest problem is inertia - that would have to be solved - one way is that Google search gets useless and people have an option to move to something better. I doubt this will happen. Other way is someone builds not just a marginally better product but a 10x better product and people move there - I don't see that happening anytime soon either.


We could have an “organic” search engine which only positions itself for “normal” webpages, and defines normal. For example, the webpage should have a title and max 4 paragraphs, on the topic, and shouldn’t include storytelling. Technical problem-answer oriented pages should only contain various aspects of the problem, but no storytelling either. Fewer phrases to index, more density of keywords, easier to index. And maybe we should come back to the rules of 1. speed 2. content being in the original HTML 3. the react hydration shouldn’t dilute the HTML.

It doesn’t matter what its artificially-defined rules are good. But people would enjoy going there better than on Google, because you’d find the organic pages.

It doesn’t matter that Google would also index them. It’s like the Panamax, it defines rules but others can use those rules to.


No need to reinvent the wheel. Just exclude from the index any websites which trigger the behaviour of uBlock Origin. Job done.


They're all doing proprietary work for LLMs.

The question is how you can be useful enough to the public without being so useful a LLM maker will snap you up


separate the ads from content, into individual columns, and never, ever shall the twain meet.


Ads aren't the real problem though, SEO and dark patterns are. Ads, even when mixed in with legitimate content, are labeled. A user can reasonably infer an ad website's goal when they click on it: to get you to pay for something.

The real problem is the system enables bad actors to do the same, without gaining the Ad label, by gaming the system to outrank legitimate (or free) sources of information.


https://www.edgedb.com/careers -

> Thank you for expressing interest in potential job opportunities at EdgeDB! At this moment, we are not actively hiring.

Posting link points to home page. So just like an ad or does the careers page need updating?


I guess that's one way of keeping Solaris alive :)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: