blinkingled

Different programming languages are very obviously not the same thing - different cp command implementations are similar conceptually to having different linker implementations that all do the same thing. But you knew that so not sure if there was a point you were trying to make there.

Writing linkers must be incredibly rewarding - go has its own, there's mold, there's LLD, there's the OG GNU bfd LD and now Zig has one too! I am sure there's a Rust one too - Wild!

Every one of them is faster than the others too lol! Mold for one tries really hard to be GNU ld and to be useful as an independent linker most have to - I guess Zig/Go ones are purpose built so at least those don't duplicate GNU ld compatibility.

Now they only need to make sure that a supply chain for replacement batteries exists, there is regulation and competition and options remain available for a reasonable price.

There are plenty of old Dell and HP laptops with replaceable batteries which can only be found on eBay or some random seller that does who knows what under the refurbishing process.

I am a full time KDE/Arch user and since Plasma 6 haven't had any HiDPI issues including monitors with different DPI or X11 apps - of which there are very few nowadays.

Tesla’s fix will involve an additional redundancy to keep the lightbar affixed to the windshield, should the glue fail.

Good news - it only affects 6000 vehicles with the optional lightbar which is dealer installed. Bad news - Tesla finds it ok to let its dealers do glued lightbar installations and can't really fix the glue failing part so they are adding redundancy.

I meant the I have no interest in knowing anything about any company's internal tech stack and also no interest in tying my application to one company's internal stack. Much of it sounded like lock-in to me.

Stopped reading at proprietary. Seriously why would I care tying my app to something proprietary and have no way out of it?

I was referring to the "HTTP request in Tokyo to find the nearest instance in Sydney" part which felt to me like a differentiating feature- no other cloud provider seems to have bidding or HTTP request level cross regional lookup or whatever.

The "decision that long predates Corrosion" is precisely the point I was trying to make - was it made too soon before understanding the ramifications and/or having a validated technical solution ready? IOW maybe the feature requiring the problem solution could have come later? (I don't know much about fly.io and its features, so apologies if some of this is unclear/wrongly assumes things.)

The bidding model is elegant, but it’s insufficient to route network requests. To allow an HTTP request in Tokyo to find the nearest instance in Sydney, we really do need some kind of global map of every app we host.

So is this a case of wanting to deliver a differentiating feature before the technical maturity is there and validated? It's an acceptable strategy if you are building a lesser product but if you are selling Public Cloud maybe having a better strategy than waiting for problems to crop up makes more sense? Consul, missing watchdogs, certificate expiry, CRDT back filling nullable columns - sure in a normal case these are not very unexpected or to-be-ashamed-of problems but for a product that claims to be Public Cloud you want to think of these things and address them before day 1. Cert expiry for example - you should be giving your users tools to never have a cert expire - not fixing it for your stuff after the fact! (Most CAs offer API to automate all this - no excuse for it.)

I don't mean to be dismissive or disrespectful, the problem is challenging and the work is great - merely thinking of loss of customer trust - people are never going to trust a new comer that has issues like this and for that reason move fast break things and fix when you find isn't a good fit for this kind of a product.

This^. Keith W on Dtrace blog said it a decade ago https://wesolows.dtrace.org/2014/12/29/golang-is-trash/

I like Go but I don't really like their NIH / replace everything with our stuff stance - esp on system tools like assemblers and linkers.

Bye Microsoft - I'm already on Linux on all my desktop and workstation machines and working on migrating off of the MacBook Pro.

It's only going to get more and more unpleasant in the commercial desktop OS landscape - need to start contributing money and effort to few OSS projects to keep the dream alive.

Yeah, what I do is make use of the freedom fully when I can and that way it's like I have fulfilled my quota for procrastination and it's easy sailing for the stuff then I need to do :D - complicated and works for me but YMMV. Feels intuitive to me lol.

If you truly enjoy the procrastination as opposed to fighting it or distracting to another thing - sooner or later you'll want to do the thing you were supposed to do.

Try that out. There is a reason why you don't want to do something and that fundamentally has to do with your mental relationship to the task - the repetition fatigue, the way you think and feel about it etc. needs a reset and enjoying the idle procrastination time gives you that.

IOW Zen mantra - when you procrastinate just procrastinate without resistance.

I am happy for a new browser/engine but I'm highly skeptical that Ladybird will ever come close to Chrome or Firefox in terms of features, compatibility and performance. It's just very hard to imagine. There's servo and look at where it is after 13 years!

No offense to anyone really but browser engines are inhumane amount of talent and effort. Might as well just keep making Firefox better.

Ugh I upgraded excitedly and can't stand the UI - there is no upside to any of it. Also for some reason things are also beachballing and VSCode keeps crashing - new M4 MBP. All the system log errors are present exactly as they were and my USB-C dock with Ethernet port still doesn't work.

I have been working on finding out ways to make use of AI a net-positive in my professional life as opposed to yet another thing I have to work around and have cognitive load of. Some notes so far in getting great benefits out of it on couple projects -

* Getting good results from AI forced me to think through and think clearly - up front and even harder.

* AI almost forces me to structure and break down my thoughts into smaller more manageable chunks - which is a good thing. (You can't just throw a giant project at it - it gets really far off from what you want if you do that.)

* I have to make it a habit of reading what code it has added - so I understand it and point to it some improvements or rarely fixes (Claude)

* Everyone has what they think are uninteresting parts of a project that they have to put effort into to see the bigger project succeed - AI really helps with those mundane, cog in the wheel things - it not only speeds things up, personally it gives me more momentum/energy to work on the parts that I think are important.

* It's really bad at reusability - most humans will automatically know oh I have a function I wrote to do this thing in this project which I can use in that project. At some point they will turn that into a library. With AI that amount of context is a problem. I found that filling in for AI for this is just as much work and I best do that myself upfront before feeding it to AI - then I have a hope of getting it to understand the dependency structure and what does what.

* Domain specific knowledge - I deal with Google Cloud a lot and use Gemini for understanding what features exist in some GCP product and how I can use it to solve a problem - works amazingly well to save me time. At the least optioning the solution is a big part of work it makes easier.

* Your Git habits have to be top notch so you can untangle any mess AI creates - you reach a point where you have iterated over a feature addition using AI and it's a mess and you know it went off the rails after some point. If you just made one or two commits now you have to unwind everything and hope the good parts return or try to get AI to deal with it which can be risky.

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.

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.

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.

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

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?

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.

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 :)

Seems premature. You don't write successful browser engines using relatively new language that is optimized for one platform.

But it was predictable - Andreas comes from Apple background so.. The other thing is no one can build a browser alone - the ability to attract the right people is what differentiates a mainstream usable browser and a toy one. IOW focusing on adding another language that is not as popular amongst the right developer demographic seems like the wrong thing to focus on at this stage.

Yes, I am not arguing against having the ability to deal with it quickly - I am saying canary/ staging helps you do exactly that. Because as we see in the case of Intel CPUs and Crowdstrike some problems or scale of some problems is best prevented.