Permik

The writing had been on the wall for a while. Hopefully this'll finally drive the usage of the site down.

As history has already shown during the Nuremberg Trials, "Following orders" doesn't absolve the individual responsibility of the people under command.

Hello, it's me, ur guy (and surprisingly, I'm a part of the new generation!). There's probably dozens of us!

In my software development career I've always specialized on the UX, accessibility and platform convention side of the UI. I can't design any actual "pretty" UIs for the life of me :Dd

Inserted edit: Ok, totally forgot to mention that I am a full-stack dev, but definitely focus more on the abstract side of UI than the actual pixels on the screen.

Aside/relevant: Did you know that click-and-dragging a dropdown/select element to use/select/activate an action is an ancient cross-platorm pattern that was almost lost to time, because almost none of the modern web component frameworks forgot to implement it? Even more emphasizes the pop-cultureness aspect mentioned above :)

Because English is the odd one out with the non-obvious mapping of sounds to character.

It could be that I'm totally yapping bullshit, but the "designing from scratch" can vary depending which field of maths you're talking about. For instance, if we model the semantics as a series of composable functions, then you only have to scratch only the specific dependency tree of the functions. Basically everything can be reused with no wasted work, and the output space gets culled.

At least in Europe, there's an argument to be made about a Nitter instance being an interoperability service for clients that do not use cookies/JavaScript, and could be argued that it's protected under the interoperability exception under EU directive on legal protection of computer programs.

The directive gives quite wide exemptions for reverse engineering, but as there's no reverse engineering here, just documenting public APIs, codifying and interfacing with them, it seems it is more than OK for the compatibility layer to exist.

Technically there is already one, it's called HypeHype, but it's using their in-house graph-style editor. Vendor-lock-in out the whazoo.

Haven't followed them too closely, but wouldn't be surprised if they'd added LLM tools to the platform.

This could be probably rectified with an ongoing dono in their GitHub Sponsonships.

Unless the data collected is of a user that is an EU citizen. This needs prior approval and consent per GDPR.

This is a shitty bad-faith argument, AND the claim you're making is unfortunately incorrect :D For example, nothing actually restricts you putting your car to bits and using the motor :) It'd be a whole another ordeal that if they'd deliberately try make the car parts to brick themselves in an unknown environment. But they do not. Makes you think.

Personally? I'd say that this is totally unreasonable. Pre-restricting the use cases of the device that YOU bought and have the ownership of is absolutely not OK.

There are a multitude other trivial ways this could be accomplished, but they chose the "lets squeeze the market" and "fuck the modders" option.

The company is a part of the society, and has the responsibility of providing support for their devices. Society provides the customers and money, and the company has the obligation of providing support.

They could just burn the serial to the silicon and when someone needs support, they need to provide the serial and they cross-reference the data tied to the serial number. Too much ram? "Yeah, sorry, we can't guarantee the operation of your device. Here's a 5% off coupon for our store to get one with our genuine hardware"

THIS WAS SUCH AN EASY MARKETING WIN :(

Don't worry, doesn't actually spoil plot of the episode, it's all spelled out for you pretty clearly at the start.

I believe it's a stylized lo-fi rendition of an axolotl.

There's the program called Starshield, that's part of the miltech side of the program. One of the military uses is using the starlink constellation signals as a passive SAR for the whole planet with millimeter scale accuracy.

I don't have the answers, but I'm speculating that it has developed first from being a skeuomorphic text representation depicting a modem/ethernet port, but then just being re-used outside the original and slowly evolving to what it is currently.

Yeah, by implicit ordering, I mean an underspecified pipeline which has an undeclared dependency on some of the inputs being sorted. Unfortunately this is why the code in the cited paper worked on some systems and not others as the os.listdir() call didn't guarantee sorted results and thus the assumed invariants were broken.

Requiring code to be explicit about its invariants by default is just plain good design and makes things more robust. And when being more exact about invariants, you can reap the algorithmic benefits.

This is a tricky field, the problem is not actually the non-determinism of the processing algorithms, but implicit ordering of the data.[1] The implicit ordering of the data is a footgun that -- as seen in the paper -- has already claimed victims. Using algorithms that don't need to upkeep the ordinality requirement in every operation will definitely move the library to a better direction and make future data modeling better and more explicit.

[1] Aha, now I see why language models use this so frequently and why it might be overrepresented in the data. This is a perfect way to move the blame from the person you're responding to, if they're mistaken. They probably have a super, super overtuned "politeness" gym using sentiment analysis that tries to reword answers to not blame the misunderstandings of the person. Then this blame shifting unfortunately gets re-used as this super, super common phrase.

Yeah, it technically was there, but it had proprietary components and Nokia had a baggage of softbware project management being super inefficient because of their earlier roots of how they developed software in their past. Not that I have personal experience of it, but a colleague of mine had first hand experience of it.

Nokia had a "means to an end" type of perspective to software, it was all made to be basically disposable and they didn't have great "steward of the platform" type of effort.

Also, if we take a gander at the timelines, unfortunately QT and Maemo were happening in parallel, and of course Maemo was based on GTK. (But QT was still a Nokia proprietary tech back then.) Right hand not knowing what the left hand was doing etc.

Not that any of this means anything, just felt that this was all relevant.

NIH barely applies here at all. If we take into account the constraints they were under and the absolute state of desktop Linux when Android started, it makes total sense.

Starting a lot of the components as greenfield projects will fortunately help a ton with shedding years and years of legacy cludge, hacks and desktop first design. Without mentioning the colossal amount of friction they would've faced if they tried to upstream any of the code they would've produced by the end. "We don't care about that issue. Closing."

Because of the above, they still would've needed to have their own fork regardless and still would've eventually diverged further and further -- so why bother? With a greenfield project, you can just optimize to your specific constraints. If the maintenance becomes too burdensome, just pick up the best of your design and reimplement them onto the non-greenfield project, everyone wins :D

  By the time you have an out-of-order core

You're thinking too high level and high performance/high power use -- think about minimal embedded controllers, no need to add the complexity of O3 exe, but there's still the possibility of getting to optimize the hazards and execution without the shared state.

Doing the deliberate choice of leaving flags out of the core and then using them in the fp ops ext will nudge designers towards "this is probably the point you should think about out-of-order execution"

Skitter creek bath salts... Or SCBS Guess there'll be a talk called Secure Computing BullShit in the next Blackhat conf! I'll be eagerly waiting for it! :)

I'm probably an outlier, but as someone working a non-physical job, I have been talking about how I personally would still keep working and doing jobs even if all of my basic needs are met.

I do work purely because of idealistic reasons. I'm not actually owed anything, I'm working because of us, humanity. Yeah, people are going to slack, and that's just life. It's just statistics, optimize society to such a configuration that people acts have a place and get the support they need. Most of the "slackers" who represent the people just living on the UBI type system you described, probably don't do it as a direct choice. Most likely they feel like they can't contribute to society, but that's something that's solvable. It's a matter of education and culture.

About your quote:

  "have nothing to lose and decide to attack the source of their misery. Bread and circuses will only distract so much."

There's a theory directly relating to this that I have about the modern golden age of punk and rock in the nordics. When people had all of their basic needs met, they finally had the time to take a breath, take a look inwards and face their own inner demons. I suggest that this was one of the big things that created the conditions which made the nordics the rock/punk powerhouse that they were.

Of course, the good times also had their downsides, lots of complacency in politics and not feeling the need to fight for better, because things were already better than they've ever been!

I think it's more nuanced than that. Obviously countries have differences on how aligned the people and the press are, but there's also the aspect of how highly educated the people are.

FWIW, I feel like the press in Finland doesn't try to "win" points by pointing out the humiliation and the utter failure of the current state of affairs in the US, because that point is plainly obvious, but the reporting more closely reflects the forces and agenda going on under the surface.

The embarrassment stuff is more for the coffee-table chitchat and having a collective sigh of relief with your co-workers that we're not so intimately close to the whole mess there.

Any new advancements regarding Rust borrow checking and allowing new code is always a very challenging exercise, as people have already accustomed to the "that style of code doesn't compile"-area of the current compiler, so the most battle hardened devs probably have a terribly challenging time of actually encountering the new, now allowed, type of code.

So cool that the mut_or_default now actually correctly borrow checks. I'll be watching for cool new patterns that this'll allow in the future!

I've got a stripped down installation of win11 in a vm that has Servo as its only browser if there's ever a need to open a website in it. It's something!

I'd like to suggest that this messaging is actually the inverse of virtue signaling, I.E. "icky signaling" for snowflakes. Keeps people at bay who are icked by the message.

You brought out a good point, it was.

It's just a statistical anomaly where the collective thought was stuck in a local minima, where they thought that the sacrifices had a correlative/causative effect on good harvest/luck/fertility/rain/etc. The collective common good for a sacrifice of someone was seen as a good deal with the limited information they had available at that time.

That's a personal information database and making one without consent of the people detailed is _super_ illegal in Europe.

There's a few examples of entities like Jehovah's witnesses making do-not-visit lists that have been considered as a personal information database and such have been in hot water many, many times about that. Yes, even though you might do them to help you personally, you're acting as an agent of the org you're associated with, and such you're not supposed to be doing that.

I haven't written up an article about it yet, but from a cursory look of the legal stuff this only affects private citizens and could be circumvented by setting up a shell company that owns your devices.

Legally, you can't surrender these devices, access to them or their passwords, as they are company property.

I'm not sure that if this is an obvious question that has been gone through already, but have any of the death threats relating to Rust stuff actually been "verified" or is it just an opinion that has been repeated enough times until it has been accepted as truth?

Just the open amount of discontent towards the language and the community, creates the perfect storm for a malicious individual to pose being a Rust developer that sends death threats for doing things that are not aligned with the values of the language/community.