HN user
The overwhelming majority of the enjoyable coffee experiences are caffeinated. While there is good decaf out there it's not the norm, specially in smaller markets.
I've had success asking it to specifically spawn a subagent to evaluate each work iteration according to some criteria, then to keep iterating until the subagent is satisfied.
Is there Live Edit support? I've literally left an agent running to automate the use of Android Studio out of my workflow when I just want to iterate on UI.
Look up protondb for game compatibility. Arc raiders is marked as running perfectly fine, but plenty of multiplayer games with invasive client side anti cheats such as Fortnite or Genjin Impact do not run. If you depend on such games it's best not to switch, any privacy concern you may have with Windows is gone with those games running literal rootkits on your PC anyway.
I've been running Linux for gaming for well over 15 years and have not missed much in the last 5 or so. There's way too many games out there to play that do run on Linux even if unemployed and have the time to dedicate it as your sole hobby.
If you generate OpenAPI specs, and clients, and server type definitions from a declarative API definition made with Effect's own @effect/platform, it solves even more things in a nicer, more robust fashion.
Now do that for 30 services and system config such as firewall, routing if you do that, DNS, and so on and so forth. Nix is a one stop shop to have everything done right, declaratively, and with an easy lock file, unlike Docker.
Doing all that with containers is a spaghetti soup of custom scripts.
OCaml is the closest match I'm aware of.
Happiness chemicals are the end result, and end result we cannot cause directly, anyway. What leads you there, how the process involves your particular brain and environment, and how it acts as a feedback loop are a higher concern.
Even if one day you could just squirt the cocktail directly into your receptors or otherwise trick them, there's more to happiness as a part of life than turning yourself into a vegetable, but I digress.
You're doing native code, this the solution is the same as in native code: your languages agree on a representation, normally C's, or you serialize and deserialize. Mixing language runtimes is just not a nice situation to deal with without the languages having first class support for it, and it should be obvious why.
Thanks for the one-liner, solved it within 30 seconds!
This is a thing and doesn't require a separate model. You can set up custom prompts that will, based on another prompt describing the task to achieve, generate information about the codebase and a set of TODOs to accomplish the task, generating markdown files with a summarized version of the relevant knowledge and prompting you again to refine that summary if needed. You can then use these files to let the agent take over without going on a wild goose chase.
I'm sorry if this is rude, but your analogy is completely off the mark.
Rules that are not fixed but still are a requirement for code to work/make sense still merit an explicit encoding in the type system. You can have an interpreter somewhere that makes sense of unstructured data and delegates to the right functions once it's able to parse and slap a type on it, which will be better than a function that has a bunch of conditionals laying around which at some point either force you to duplicate them or make assumptions you're calling the right functions in the right order.
Governments are elected every now and then by large sums of people as a package deal for handling a number of issues, and only one is in place. Products and companies exist in multiples and regardless of how big they are, they're still more targeted, and you the consumer get to choose directly and every day.
https://www.merriam-webster.com/dictionary/regime
https://en.wikipedia.org/wiki/Regime
Relevant quote: "In politics, a regime (also spelled régime) is a system of government that determines access to public office, and the extent of power held by officials. The two broad categories of regimes are democratic and autocratic."
It is true that as a term it has accrued some negative connotations due to the frequent use of the all-encompassing "regime" to speak of governments where their exact denomination tends to fall on the autocratic side of things. From a journalistic point of view, it is better to use a neutral term than a charged one; which unfortunately as you've noticed yourself it can taint the term to readers who are not familiar with its exact scope.
But it is correct to call it Biden's regime, just like the current administration (perhaps a better term given its popularity in the US) is part of Trump's regime.
That's way too expensive for an "affordable EV".
The BYD Seagull retails here in Uruguay for less than that and we tax cars at about 100%. On China it seems to go for 10-12k.
It's a proper, basic city car. 4 to 6 air bags, ~300km range (more than what this article's car indicates), all basic security features and standard gadgets out of a modern car.
Our EV infrastructure is not viable if you don't have a charger at work/home and yet these have sold like hot cakes.
Legacy carmakers are making increasingly worse ICE cars for the most part (btw does GM sell a C-segment hatchback on any market, anymore?) and their EVs are simply uncompetitive. What's it going to take for them to wake up to the fact they're going to have to stop fleecing their customers with crappy products? Bankruptcy?
Finally one of the big ones drop a conversational assistant based on modern LLMs.
I'm just hoping this is what it takes for Google to follow the trend for Android Auto and they go through with their internal integration experiment, don't care if I have to pay a fee, I just want it to understand my accent and be useful consistently.
On NixOS it was as trivial as `podman.enable = true;`. IIRC on Arch it was just a matter of installing the package.
It's all daemonless, rootless and runs directly with your host kernel so it should be as simple as it an application of this kind gets. Probably you followed some instructions somewhere that involved whatever the podman equivalent for docker-machine is?
I've been interviewing a bunch of developers the past year or so, and this:
Architectural interviews are likely safe for a few years yet. From talking to people who have run these, it’s evident that someone is using AI. They often stop with long pauses, do not quite explain things succinctly, and do not understand the questions well enough to prompt the correct answer. As AI gets better (and faster), this will likely follow the same fate as the rest but I would give it some years yet.
Completely matches my experience. I don't do leet code BS, just "let's have a talk". I ask you questions about things you tell me you know about, and things I expect of someone at the level you're selling yourself at. The longest it's taken me to detect one of these scumbags was 15 minutes, and an extra 5 minutes to make sure.
Some of them make mistakes that are beyond stupid, like identity theft of someone who was born, raised and graduated in a country whose main language they cannot speak.
The smartest ones either do not know when to stop answering your questions with perfect answers (they just do not know what they're supposed to not know), or fumble their delivery and end up looking like unauthentic puppets. You just keep grinding them until you catch em.
I'm sure it's not infallible, but that's inherent to hiring. The only problem with this is cost, you're going to need a senior+ dev running the interview, and IME most are not happy to do so. But this might just be what the price of admission for running a hiring pipeline for software devs is nowadays. Heck, now feels like a good time to start a recruitment process outsourcing biz focused on the software industry.
The article indicates these are also options:
2) Request a $100 Google Store credit that you can put toward the purchase of another Pixel phone or other hardware.
3) Request a $50 cash payment.Are we really pretending multi-monitor on X is not an absolutely shit show? Try mixed DPI and VRR in one of the monitors and see how you get that working well.
Because both are ubiquitous to the point they basically dominate a large part of a usecase's toolspace.
I believe this poster meant the new Linux driver for Nvidia cards called Nova (announcement: https://lore.kernel.org/dri-devel/Zfsj0_tb-0-tNrJy@cassiopei...), not the driver maintained by Nvidia.
I've given up on Home Assistant because of this. Particularly because since I've switched to NixOS I really don't want to be arsed reconfiguring stateful crap from the start every time I make some change that requires a reinstall.
Sadly, I've yet to find a viable alternative.
Re-reading it I can see how it could be perceived by some people as such, thanks for pointing it out. There's probably better phrasing or adding more context could make it more amicable:
The goal was to explicitly tell people not to bother "just reading it" as one (and by one I mean myself and most people I know, surely there are exceptions) is naturally inclined to do unless something is particularly piquing our interest.
Without engaging in active, conscious effort, syntax that is different than what we're used to (specially something as established as SQL) where the changes aren't groundbreaking at first glance can easily make us dismissive without realizing the benefits. And after seeing it too many times with all kinds of technologies that stray away from the familiar, I just want to prepare the reader so that their judgment can be formed with full use of their faculties rather than a reflex response.
https://prql-lang.org/ has a bunch of good examples on its home page.
If you engage the syntax with your System 2 thinking (prefrontal cortex, slow, the part of thinking we're naturally lazy to engage) rather than System 1 (automated, instinctual, optimized brain path to things we're used to) you'll most likely find that it is simpler, makes more logical sense so that you're filtering down things naturally like a sieve and composes far better than SQL as complexity grows.
After you've internalized that, imagine the kind of developer tooling we can build on top of that logical structure.
This is for all intents and purposes, fp-ts 3. The projects essentially merged, Giulio Canti is working on it and fp-ts 2 is renaming methods to ease the transition to it.
In the same vein of interesting experiments on weird cables:
ADSL on wet string: https://www.revk.uk/2017/12/its-official-adsl-works-over-wet...
So it's not really something intended to be efficient and useful, it's a conversation piece.
Does not care about flakes and does not care about adding types, the most important omission in Nix. A minor performance bump seems unlikely to make me want to boil the ocean.