9,915 karma · joined May 15, 2015
- it needs to be properly announced to all eligible voters
- be declared as binding, you can't tell people it isn't a vote and later on declare it is
- the platform for voting needs to work
It is a misconception, that "noon" is the middle point of your awake time. That was never the case. Our day usage most of the time is asymmetric: start the day and especially the work with the sunlight, spend the evening time off after work after sun set.
Using the high point of the sun as the reference for the daytime is a very practical choice, as this is the one easily observable time point which doesn't move much over the course of the year (a few minutes, but that is symmetric).
In my personal opinion, the only reasonable decision would be to permanently return to the standard time before the introduction of DST. Because otherwise the whole European timezone would have to be redesigned.
If you want a longer version: open source software under the normal licenses give you irrevocable rights to use it, as it is open source, you can also administrate it. You have full control over it. That was the core of my statement. Additionally, European authors are major contributors to many of this software. So in what exactly do you disagree with me?
Writing now about it, I think I could do it with a torus, where the radius of its cross section is the small radius, the torus radius is the large one, take two of them, add two cylinders to only keep one quarter edge and then take a quarter of the resulting bevelled disk.
Or if you turn your argument around: if people depend on workflows and automation (I do of course too), then this is a good reason to standardize the diagnostics and errors of the checking tools to the point where the workflows and automation can depend on them. Otherwise they will remain tools which are completely optional to run, or even worse, are not part of your normal work flow.
The topic of "European" programming languages is highly interesting in the sense that there were a lot of highly developments done in Europe, but they are often less noticed than the counterparts popular in the US. The reason to look more into them would not be so much today's independence, but more to resurrect good concepts that kind of got ignored by history.
There is the ISLisp standard, of course the treasure chest of languages and works boy Nikolas Wirth and so much more. Europe has many great universities, their creations usually are free.
Of course, you could call Python an European language and Go heavily draws from the Wirth's language family.
What we do need now is finally the determination to fight climate change. We have all the tools at our disposal to eliminate any fossil fuel burning within some years. We should finally take this as the priority it should be.
The power of this is that this function is also written in plain Lisp and it also sees all definition already existing in your Lisp image. Also, it is completely unlimited in power. So while being run, or as it is called "during macro expansion" the function could google for one of the things passed and use the result to create the output. Of course, this is not a practical example, but shows how flexible the system is.
Any style of writing you are not familiar with will require a lot of training. Try reading anything written in the Greek alphabet for example.
Yes, it is a long journey until the whole energy consumption is moved to renewables, but running the electric grid of a country like Germany to way over 60% on renewables is an important point on the way there.
Still, there are a few things which could be improved relative to the current Studio. First, the ability to easily clean the internals from dust. You should be able to just lift the lid and clean the computer. Also, it would be great to have one Mac which you could just plug in a bunch of NVMe disks.
On the other side, they might replace the Mac Pro with a rack mountable machine as the demand for ARM servers in the cloud raises.