Some reports indicate it is already to late for emission reduction, or even elimination, to halt the feedback effects that continue the trend. But it won't be too late for active climate engineering until the effects of the climate change prevent our ability to do that engineering.
Is Gemini really that bad? I mean, I would always prefer anthropic for agentic coding, and apparently openai has the math thing cornered, but if I'm using ai like a search engine gemini does that just fine. That may be all they were actually aiming for whatever else they say.
I would not have chosen the word governing for that sentence but I'm not sure what fits best. Plundering, pillaging, gutting, ransacking, Rick rolling, despoilng, or perhaps molesting.
I know this isn't /. but a car analogy seems appropriate here. A city is like a modern cramped engine bay vs an old one where you can sit next to the motor to work on it. Anything you try to fix or upgrade in a dense city causes large problems.
Also, governance isn't like manufacturing, it doesn't get easier at scale, it gets so much harder.
Living in a perfectly planned super dense urban utopia where I can quickly walk wherever I want is extremely appealing to me. I would also like living in the wilds where once a week I drive to the general store and back as the full day's task. Suburban living is my least desired outcome. But everywhere there is room for it, it happens, even without a city to latch onto. There are good reasons for that.
The climate part is certainly an issue for dfw, but the superiority of dense urban areas from a financial or ecological standpoint isn't backed by data. Buses were better for fuel efficiency, but now the bus and robotaxi are both ev, the robotaxi has a smaller impact ecologically due to microplastics scaling with axle weight ^4 and financially because road wear scales with axle weight ^3. If buses and trash trucks didn't drive on streets they would last virtually forever the way they are built now. While the glorious excesses of the last 75yrs are definitely going away, the suburbs may very well not. Urban cores might instead rot in infrastructure until only the highways between them with low density adjacent settlements remain.
Lots of single user "busses" cause dramatically lower road wear and microplastics than a many user bus. Those scale with axle weight to the third and fourth powers respectively.
How does this relate to the topic? I'm willing to assume it does, I just don't get it. I'm probably overreacting because when Scott was writing this, tens of thousands of Scots living in poverty were being evicted via arson from their land and country. Saying they were dead in spirit is very elitist as he sat in comfort.
A good example is go. On linux you can use a from scratch image fairly easily because it only uses syscalls. But for windows or mac the moving target wasn't maintainable so they link against shared objects. Linus enforcing the don't break userspace rule is what made that possible. That definitely has tradeoffs. At some point relibc or something similar will allow the same (stably) for rust. But using posix as that compatibility boundary gets you a much larger set of OS and only occasionally has a performance penalty. Often, a posix api tuned to the kernel is more performant. Musl is an exception precisely because it makes an openbsd-esque trade of performance for simple small attack surface.
Even if you don't think about memory management, and do the naive thing in rust or rc in some other systems language, gc only comes out ahead in that many tiny objects case. Which is very domain specific. I don't ever run into that situation, or if I do, they are homogeneous in type so I handle them in bulk, not individually.
Yeah, but its always a trade right? Heroin would kill me too fast for the upside. The trade on alcohol wasn't what I thought it was. I think there are better options. Says I as I lift a cider.
Have the recent studies indicating just how dangerous alcohol consumption is made any impact. Losing a few neurons was one thing but some of the studies don't put it as much less dangerous than tobacco. New guidance in the US is there is no safe quantity and no one should have more than one serving a day. I know a lot of younger sw devs in the US that simply do not drink ever. I once would have said that was a little unusual, but now it is the norm. I suspect it will be stigmatized akin to smoking not that far into the future.
We got one of the greenpans for eggs after the last ptfe one chipped. It is ceramic glass coating of some sort. About halfway between ptfe and mirror stainless for sticking. Better than that if you keep the temp low. Kinda pricey though.
In my experience, it will go to every length to convince you it has ported code that it hasn't. It will silently drop upstream unit tests it has no code for, if questioned it will insert some markdown giving some rational why that specific bit was deferred, after the fact, and then point you to it. This was Opus 4.6 for reference. I have had much better luck with small numbers of higher level tests that I can individually verify equivalency. I haven't tried having it do differential fuzzing on some high level interface, that seems like it might work in some cases. But to summarize, treat it like an adversary trying to deceive you.
That was certainly true once, but now all that state is serialized to xml amd zipped up. You can unzip it and look at it if you don't value your sanity.
If you are writing a lot and have dysgraphia, a cheap fountain pen like pilot varsity ($2) or platinum preppy ($7) can help you fight the excessive pressure we tend to use leading to less hand cramping. Using tools that make you write more because it is more enjoyable is good, using tools that make you spend time thinking about tools is bad. I really liked those tiny comp pads cvs sold, but I haven't seen them in a while and I don't like the dollar store ones. I just grab random pads that aren't bigger than my phone so they sit nice in my pocket.
Relatively inexpensive plastic semiauto pistols, ruger is overrepresented, are purchased in small batches by people either pressured into it or who make their living marking them up and reselling to people who couldn't pass the background check. The majority of those sales go through a small number of known registered firearms dealers. The straw buyers are the ones breaking the law, but the dealers who knowingly selling to them aren't. There should be some policy fix, but the best I've seen is a state that limited purchases to 3 per month per person. It drastically slowed the flow into those groups driving up prices as old ones were recovered from crime scenes etc. Money and macro also has a good episode where they talk about how neighborhood beautification worked better than gun control for this type of violence. The scary rifles get used by the mentally ill because they look scary, and the large number of deaths at once combined with the inability to control your risk and the more privileged socioeconomic class of those harmed makes it more visible.
That does seem to be the way many use it. I'd be very surprised if they didn't have to insert a rule to prevent opus from constantly asking why they didn't just use ncurses. I just asked sonnet for design options for a tui to onteract with llms to perform sw dev tasks. After describing the tui it immediately suggested ratatui and crossterm as the tech stack. I feel like they must have ignored even the advice of their own llm to come up with this solution.
Edit, the sonnet question shouldn't be taken as proof, it knows I'm a rust dev.
The criticism didn't appear to me to be that the solution didn't work, just that many of the working solutions we are selecting are dangerously overcomplicated due to shortsighted decisionmaking. The benefits of throwing redundant stacks of abstraction atop each other in terms of time to market are questionable, and obviously absent in every other metric.
I don't use it to ship whole products. I have it do some tasks.
I have it code dsp techniques in journal articles I hand it. I have it create the unit tests, pipelines documentation. Then I manually verify the test cases aren't wrong and run the tests. If they pass it does what I wanted and I start looking at the code quality. It varies from being better than I could have done it to being objectively bad. I fix it if it needs fixing, then I'm done.
I have also pointed it at issues in our backlog and it usually finds the subtle logic errors underlying the behavior in the issue.
I haven't started and entire product from zero and shipped it. Mostly because I haven't started a new product since it was capable of that. But also because it has a scale beyond which I don't find it as useful. I have used it for an entire repo, but in the crates.io or npm scale of repo, not boost scale.
The question I would ask next is that if a majority don't actually favor it, who will vote to sanction member countries that refuse to implement it in protest? Giving a central authority significant power likenthis inevitably leads to autocracy per Montesquieu.
Ukraine seems pretty paranoid about this, having backup suppliers for parts. Looks like they take efficiency hits and build more complicated things out of multiple discrete chips that would normally be ontegrated commercially so that they can go to suppliers in Oceania, eurasia, or eastasia depending on who is being helpful.
I think I have some bias. I like rust. I like using opus, I don't want to use zig, don't see the point for it, but I find it aesthetically pleasing. I don't use JavaScript I wish it would disappear. If I did ise JavaScript I wouldn't run it on bun. Some of those tilt me either way. I agree with the LLMs take on the tone. The result of the two posts is that I think Jarred is a poopyhead, andrew is a bit childish but genuine and I'd probably like him, and I still won't use zig or bun or JavaScript. I plan to keep using rust and opus.
The borrow checker really isn't that bad. It isn't like they were porting from something with GC. They were already having to think about these things anyway. Even then opus seems to have no difficulty going between c# and rust while respecting the idioms of both. No unsafe needed. Zig should be even easier except the lack of a training corpus for whatever frankenversion of zig that bun was using.
GMO hyper competitive feral cat colonies that ignore birds and pollinate gmo soybeans whilst collecting for their kitten hives. Each claw is of course a stinger. What could go wrong.
If you are willing to hand code intrinsics it doesn't really matter what language you pick from a performance perspective. Rust consistently shows it has better performance than c++ in code that does not hand code intrinsics. If cpu(not gpu) based performance is all you care about there is no reason to pick anything but rust. Modern c++ devs have no trouble with the borrow checker either they are already doing all the things that keep it from complaining. The reasons someone might not pick rust involve integration with existing code, the complexity of the language, and the depth of it's dependency trees. The complexity argument certainly doesn't lean you towards c++ or probably anything with an llvm back end. The openbsd approach to c is probably as simple as you can get these days short of forth or something equally obscure. Dependency trees are deceptive. We all have deeper trees than we think we do, but the rust front end itself has well over 100 crates in its tree...