jcarrano

I picked up a carbon-steel pan at IKEA because that was all that was left. I knew it takes some work to season. I did not know there's a whole community of carbon-steel nerds committed to getting the most perfect seasoning to fry an egg. Now I know more about the topic than practical or necessary.

We started out with the Motorola HC11, I'm guessing because someone used it a lot on the past and no one wants to redo all the course material. We used a simulator called "Wookie".

Despite being somewhat obscure, it has the advantage that it is easy to understand while also being real. We had a board where you could hook into the address and data busses, since the memory and busses were external. Also, it has a simple bus, as opposed to an ARM chip with AHB, APB, etc, and no pipelining.

What's the advantage of IFUNCS, over putting a function in the library that selects the implementation, either via function pointers or a switch/if? In particular given that they seem to be quite fragile and exploitable too.

I don't have much experience in low-level optimization, but would a modern CPU not be able to predict the path taken by a brach that tests the CPU features.

There are insurance companies that insure insurers. At each lever there are solvency requirements.

Maybe it would be better if the agent would help people submit better reports instead of trying to fix it. E.g. it could ask them to add missing information, test different combinations of inputs, etc. I could also learn which maintainer to ping according to the type of issue.

Those monetary tricks only work for a short time, in this case until workers realize that not getting a rise roughly matching inflation is effectively the same as a getting paid less (i.e. Rational Expectations).

Lua can certainly work, though it takes up a bit more ram than absolutely necessary due to it allocating language data structures (tables mainly) during startup. If you have enough ram it is fine. I ported Lua to the RIOT OS and it was not all that hard.

Leonard Read had the same feeling when he wrote "I, Pencil". Here [1] you have it narrated by Milton Friedman.

[1] https://www.youtube.com/watch?v=67tHtpac5ws

Crime does not scale. It's the same few people stealing the majority of bikes. I'd go as far as to claim almost no thief steal only one bike.

Catching thieves and jailing them scales. For each one caught you avoid potentially hundreds of further thefts from that person and an even greater number from the people who will be discouraged from pursuing criminal activities.

In primary school they banned marbles because they would cause conflict. They also banned other things (cards? I forget) for the same reason.

How on earth will children learn to deal with and solve conflicts if conflict is banned??

My Citizen ana-digi-temp from 1985 works perfectly fine and shows Feb 29.... though it thinks it is 1996!

Strictly speaking it should say "1-trit LLM", or, as they later mention 1.58 bit.

I will sit down with XFCE and X11 until the sharp edges have been filed and I will switch when wayland is mature.

I'm really thankful for the people sacrificing their time to test all this stuff and experiencing the bugs. I, as much as I like the GNU/Linux desktop, have already suffered through enough system changes and now I need my computer to get actual work done.

I feel updates used to break thinks more often and now everything works mostly fine. I remember long ago the issues with Polkit/dbus policies, changes in xorg drivers, the introduction of pulseaudio and then pipewire, systemd, GRUB2, problems with removable drives (that are thankfully solved since long), etc.

Good points, but this is not something you can solve with a recipe. Investigate, talk to people and make sure you are solving actual problems and prioritizing the right tasks.

This is an extremely crucial step that you must do first: familiarize yourself with the system, its uses and the reasons it works like it does. Most things will be there for a reason, even if not written to the highest standard. Other parts might at first sight seem very problematic yet be only minor issues.

Be careful with number 4 and 5. Do not rush to fix or rewrite things just because they look like they can be improved. If it is not causing issues and it is not central to the system, better spend your resources somewhere else.

Get the team to adopt good practices, both in the actual code and in the process. Observe the team and how they work and address the worst issues first, but do not overwhelm them. They may not even be aware of their inefficiencies (e.g. they might consider complete rebuilds as something normal to do).

My feeling (I've worked on EVSE's but not particularly Plug and Charge) is that standards end up being overly complex with too much potential for different implementations to disagree.

Even something as simple as charging control via control-pilot/proximity signals is already problematic with some vehicles.

Maybe because I'm an engineer and not a business guy, I do not understand why not implement the bare minimum that works and leave advanced cases for later.

Means that the X server directly communicates with the display driver to do the low-level rendering. Compare that with Xwayland, in which the server is an application talking to wayland or Xephyr which renders to a frame buffer in another X.

Excellent! 200 years ago escaping poverty was not possible, 100 years ago it took a couple generations and now a mere 20 years.

Holding a fixed position on a double integrator system (like a hovering drone) in discrete time is a nice problem too.

Just get any computer that you like and put any Linux distribution that you like on top, and you will get effectively infinite support with a proper OS and not a toy.

Yes, and the next step is that the vendor will sue researchers for posting CVEs which they consider "bogus", accusing them of hurting their business.

It's not so much as open source becomes a liability, but rather "well known", whether open or not, becomes a liability. If you pull a random json library from github that does not even appear on any vulnerability database then you will probably be fine.

What's the problem with using JSON and providing a schema? It is not so "pretty" to write with braces, quotes and such, but not too hard either. I have been doing that at work for some time now. VSCode will even recognize the schema and check the document in real time.

As I mentioned a couple days ago [1], this problem will get much worse in the EU with the upcoming CRA. Either the only software vendors left will be big ones with the capacity and leverage to counter these CVEs, or companies will turn to obscure, bug-ridden software which have no CVEs because no one bothers to research them.

[1] https://news.ycombinator.com/item?id=37582808

Maybe we are at "peak green", i.e. the moment in time with the greatest amount of green policies. Then, from this point onward we should see a decline in green commitments.

Setting aside whether "peak green" is or not a bad thing, if you consider the premise of the green transition according to its supporters- government hastening a change that would otherwise be too slow- then the phenomenon is inevitable. If initiative followed (lagged) capabilities (technological-economic, geopolitical, social) then we would probably see a smoother, slower transition. Any attempt to go faster than capabilities allow will result in a "peak green" moment (there can be many).

In summary, in a green transition not driven primarily by market forces, expect to see several of these "setbacks".

I recently read an post by the main curl developer about his troubles with a bogus CVE which was categorized as critical. The CRA's requires disclosing all vulnerabilities within 24h to a government agency. If your product uses any number of well known open source packages, there will always be new CVEs, most of which will probably not affect the security of the end product. I can't even imaging the burden it will place on companies, to have to justify whether or not each new "vulnerability" is or not relevant in front of a government body.

I suspect many will opt to use lesser known, proprietary components which are probably less secure but have less vulnerabilities reported.

While I laud your effort, having had to do such a chore myself[1] you are missing the point of bureaucracy. The whole point is to make work for bureaucrats, and the easier and more pointless it is, the better. There are also other issues remaining, like the fact that you need to involve your landlord[2].

Do you think anyone at the Bürgeramt has any reason to change their easy "just type stuff and press buttons" job to anything resembling real work? Bureaucrats wield political power, at the very least because they vote like anyone else, but they also have more direct influence than average people. Politicians have no incentive to go against them and, as long as they promise that everything will remain the same, they will have the support of the paper-stamper class. The bureaucrats form a distinct social class with their own interests.

If there was any will to solve the problem, it would have been done already, even without technology. Most people think that taxes are levied to pay for services, but it is actually the other way around, bureaucracy is there to justify the taxes.

[1] I had to go to Lichtemberg because it is was the only office with an appointment in a reasonable time frame.

[2] There are people selling registrations now.

The part about typing it again by hand and printing it is very real!

Totally nonsensical. Even from a basic energetic calculation it does not make sense. Assume:

- Photosynthetic efficiency (sunlight to starch) 0.5% for typical crop plants [1]

- Average daily sunlight of 5kWh/m2 [2] or 18MJ/m2.

- Daily requirement is 8700 kJ for adults.

With 200 sqft you will only get ~1700 kJ. Even if you a had a cow stomach that could digest the entire biomass of the plant (2~3%) you would barely make it.

And then there's the issue of where you will get any nutrient other than carbohydrates.

[1] https://en.wikipedia.org/wiki/Photosynthetic_efficiency

[2] https://en.wikipedia.org/wiki/Solar_irradiance

Thanks for the info. I'm not into game dev and did not know that. That was a pretty nasty move and they should't be trusted anymore.

The last part I do not agree: a license cannot be changed retroactively if there is no provision in the original license for doing so, and no open source license have that. Even if "revoking" licenses for all prior releases were allowed, it could only work if all copyright holders agreed, which is not practical for most projects.

Curious there is no PoopRecord, considering how important that is.

Did they make a commitment in the first place? It is up to the developers using the engine to make due diligence and inspect the terms of the contracts and licenses of the software they use.

I would feel very uneasy if my product was based on a framework, where the provider makes no commitment and reserves the right to change the licensing terms at any time.