xemdetia

One thing that was sneaky was that how the rust coreutils are laid out invalidated a bunch of AppArmor.

IBM is training their own models (for instance IBM granite) as well as watsonx as a platform. They are trying to build a products for enterprise as well as their specific AI modernization models.

I have been having great luck with waypipe (gitlab) as an X11 forwarding alternative (OS X to Ubuntu 24.04). The setup was relatively painless and it 'just worked.' while this might not suit your needs for other reasons I was pleasantly surprised.

I thought JavaScript language equality quirks was seen as problematic not a missing feature in Python.

This article is pretty frustrating as it doesn't introduce rowan or green trees and I had to read a bit to know you were even talking about a rust lib. Beyond that I don't know if I ever encountered a modern syntax tree lib that didn't have at least a pointer to the beginning and end of the token lexed at the leaf node level. If you don't have this error reporting becomes either awkward or complicated for the developer or the end user.

The health insurance is the part that just is hard to relate to much of the world which is where the fear/sadness comes from. It is the undertone in any wealth discussion. So many people in the US see their family and friends get medically bankrupted for one reason or another and insurance being tied to employment makes everything awful.

The fact that you simply can't save enough to get medical care is foundationally depressing.

The only thing I find scary about the current AI is how many AI companies became completely untethered from basic ethical controls openly. There is no facade of decency and it seems like a lot of them are running from their own shadow. I feel like there is a middle ground that could have been taken to bring content experts in instead of looting the web the world has built.

I believe what the commenter is suggesting is that since this is supposed to be machine readable then why not start with a common format like JSON similar to how things like MCP serve what functions are available or an OpenAPI spec. Generate the JSON and serve that from the well known directory.

People serve plain JSON all the time. This proposed standard is essentially a structured file anyway.. why not YAML? Why not INI? Getting away from bespoke unicorn file formats has been good for everyone.

How is using a standard path 'just for sysadmins' again? You are introducing something new today.

Maths can be super deterministic but often difficult to compute because of concepts like inferring by induction. I had to personally unlearn and rebase my understanding of math based in computation to 'get' pure maths. Another example is set building. You often don't need to compute the existence of members of sets in pure math you just need to agree that there are some members of a set that meet the criteria. How many or how many things that aren't in the set aren't meaningful often times to accept something and move on with the proof. From the computing perspective this can be difficult to put together.

From my perspective depending on where they want to develop it might be trivial to add something time consuming to a proposal such as eminent domain or easement reviews that will run out the shot clock and drown out reasonable questions by local governments. Local governance often is complicated by local (town), regional (county), and state level roles. Additionally depending on the area not all of these roles are even staffed by people working on it full-time.

This really isn't an all or nothing sort of situation. Many of the AI players have a proven record of simply not following existing norms. Until there is a consumer oriented player who is not presuming that training on my private data and ideas is permitted it only makes sense to do some stuff things locally. Beyond that many of the companies providing AI have either weird limits or limitations that interrupt me. I just know as an individual or a fledgling company I am simply not big enough to fight some of these players and win, and the compliance around companies running AI transparently is too new for me to rely on so the rules of engagement are all over the place. Also don't forget in a few years when the dust settles that company with that policy you like is highly likely to be consumed by a company who may not share the same ethics but your data is still held by them.

Why take a chance?

This was also introduced in the same moment as a bunch of real name initiatives from multiple companies. People were rejecting it based on what it demanded compared to what was offered. It also killed or force reworked other Google products that were working fine to end users (e.g. Google Talk).

In my eyes it was one of the key moments that put them on a downward trajectory in public opinion. So while it might have had the right features the rest of the deal sucked, and people were already tiring of social media overall.

I was about to be annoyed until you said you got preprod units. I guess I'll have to build on this when my desktop shows up.

I think the thing you missed is how aggressive their firings had been. It is quite possible that they no longer have capacity to maintain a distribution. Public reporting indicates 5,000 people let go... but probably more were guided to leave.

If that is the case then terminating Clear Linux as a distribution might be the responsible thing if they were the source of direction for the distro. This was also a PoC distro as opposed to seeking enterprise workloads so it also seems reasonable that after the innovations that were good were adopted by more mainstream distros they no longer served a purpose.

I still expect to see a steady stream of kernel patches for new chips and features. I just would place headcount loss and accomplishing everything they set out to do with the distro over FOSS malice. Unlike many of the ghosts of malicious corp open source this doesn't fit exactly in my view.

While not at Google for myself a lot of the CI test failures just become knock on effects from complex interdependent CI components delivering the whole experience. Oops Artifactory or GitHub rate limited you. Oops the SAST checker from some new vendor just never finished. Even if your code passes locally the added complexity of CI can often be fraught with flaky and confusing errors that are intermittent or run afoul based on environmental problems that particular moment you tried.

I find this to be an interesting anecdote because at a certain level for a long time the most helpful advice you could give is what would be the best reference for the problem at hand which might have been a book or website or wiki or Google for stack overflow and now a particular AI model might be the most efficient way to give someone a 'good reference.' I could certainly see someone recommending a model the same way they may have recommended a book or tutorial.

On point of discussing code.. a lot of cloud frameworks are boring but good. It usually isn't the interesting bit and it is a relatively recent quirk that everyone seems to care more about the framework compared to the thing you actually wanted to achieve. It's not a fun algorithm optimization, it's not a fun object modeling exercise, it's not some nichey math thing of note or whatever got them into coding in the first place. While I can't speak for your father I haven't met a programmer who doesn't get excited to talk about at least one coding topic this cloud framework just might not have been it.

I am worried about a more modest enshittification. I am already starting to encounter models that are just plain out of date in non obvious ways. It has the same feeling as trying to remember how to express someone on how to troubleshoot windows over the phone for two versions ago (e.g.: in vista this was slightly different).

As far as I can see it is just strawmanning the federal workforce as a boogeyman. Every federal person I heard of or talked to spent most of the weekend and Monday trying to understand how to respond and what was permitted to disclose. The email looks like a phishing email because it's not from existing org structure. Most fed employees never have interacted with OPM before because that's not how any of this worked. It also doesn't help that the email before this was 'if you respond to this email you resign.'

I find this fun because I always described this metric as 'time to cow.' I suppose a sheep is fine too.

I think in modern times because you don't see it the same way you forget that a newspaper, magazine, encyclopedia, academic paper, and a reference book are different for a reason and do not have to be unified, and there was no need to do so. Having a way to publish contemporary articles vs building an effective knowledge reference are different goals. The physical print production was part of the language of intent. A blog with a contemporary note of an obscure Ubuntu upgrade issue is often the best way to describe it whereas a wiki with a current reference of now the fundamental baseline of relevance. A wiki eschews the most relevant details the same way an encyclopedia focuses on the core points. As a writer I need many formats and as a reader I cherish many formats.

I feel like this missed the relatively straightforward https://github.com/emacsorphanage/git-gutter package which I feel does a pretty good job and does exactly what I want.

It has been crazy since before apps were 'apps.' It is a simple flow chart to me: do I need to interact more than once a month? No? Should probably be a website. The only time I want an app is for things I check more than 50 or so times a day, but that is because the UI for phones is awful and it is more convenient to context switch. Needless to say I find messaging apps to be the only ones that qualify.

Depending on the market it is still possible to be profitable. There is still a market even though it is narrow and most stations solve the problem like how Stephen King did- you have multiple stations to increase inventory.

When I did a roof replacement two skylights needed to be replaced and I was offered 3 options. One was purely mechanical, one had a simple remote, and one that required an app! Naturally the app one was the super premium trim.

Am I just so old to know that tying a permanent house control to a platform that can go away like say palm or blackberry or windows xp (vista driver signing) or support for the current wifi standard is slightly ridiculous? Especially for a 30 yr+ purchase?

If I want to be positive about smart home stuff I just share my confusion that the industry didn't standardize on PoE(power over Ethernet) and just give the end customer an Ethernet switch or switches that most novices can figure out and is trivial to transfer to the next homeowner.

Emergency vehicles are the kind of vehicles I don't really want electric yet. Power goes out when there are emergencies, and then what? They break out a bunch of beater crown vics?

Also inevitably lithium packs are the last thing I want to bring more of to an emergency.. imagine bringing more lithium to a California wildfire when most fire depts struggle to extinguish packs in the most favourable conditions.

Smaller clusters are common because it depends on what you are trying to accomplish. It's the same problem as any distributed system- going wider with a map only works if you can perform a timely reduce. With checkpointing you run into things like network storage being too slow and so on. There's also the fact you might want to work on/with many models and what you want to do for production (inference) is different than what you try to accomplish in development (training).

I think that one of the issues that really hurts the advertising is that the sports betting adverts will pay above and beyond what anyone else pays and it prices everyone out. It's the same problem we had with crypto and cigarettes. They need to spend infinite money to normalize their desired behavior. I feel like advertising for casinos around there being interesting non-gambling activities (e.g. concerts) is the right kind of indirect advertisement, but by necessity the online slots and online sports betting is monotone towards the outcome.

That is an interesting Safari feature for private tabs, when I start needing to have more than two levels of isolation past the non-private universe and the private universe I start using profiles. My intuition that my private tabs are logged in and I can open more tabs with the same credentials is a big part of my workflow so I never thought of needing that further isolation.

I would agree without even the caveat of the maintainer being busy. When a maintainer receives a massive changeset they have to then recover why the task was taken on in the first place and understand any decisions to get to the same outcome presented in the changeset provided. The more logical complexity that this change represents whether it is 3 lines or 3000 lines still needs to be understood by the reviewer as not breaking the rest of the system and equally can be 'massive.' The further you get from an N+1 change into a N+5 or N+6 change is where you get into situations where a N+3 change is flawed based on the rest of the system and invalidates large parts of the changeset, and that doesn't resolve all the issues or concerns.

I think a lot of people forget that changesets are sometimes not the most straightforward way to express ideas. They (including myself) also forget that while you are working with a change in front of you it's obvious but in one month it could be opaque. A maintainer is often giving you the perspective of you a month later who built on this system you changed.