Enough of that crazy talk - plainly WheeledDeviceServiceFactoryBeanImpl is where the dependency injection annotations are placed. If you can decide what the code does without stepping through it with a debugger, and any backtrace doesn’t have at least two hundred lines of Spring boot, then plainly it isn’t enterprise enough.
Fair enough, though. You can write stupid overly-abstract shit in any language, but Java does encourage it.
Succinctly and well put.
Well now. My primary exposure to Go would be using it to take first place in my company’s ‘Advent of Code’ several years ago, in order to see what it was like, after which I’ve been pleased never to have to use it again. Some of our teams have used it to provide microservices - REST APIs that do database queries, some lightweight logic, and conversion to and from JSON - and my experience of working with that is that they’ve inexplicably managed to scatter all the logic among dozens of files, for what might be done with 80 lines of Python. I suspect the problem in that case is the developers, though.
It has some good aspects - I like how easy it is to do a static build that can be deployed in a container.
The actual language itself I find fairly abominable. The lack of exceptions means that error handling is all through everything, and not necessarily any better than other modern languages. The lack of overloads means that you’ll have multiple definitions of eg. Math.min cluttering things up. I don’t think the container classes are particularly good. The implementation of pointers seems solely implemented to let you have null pointer exceptions, it’s a pointless wart.
If what you’re wanting to code is the kind of thing that Google do, in the exact same way that Google do it, and you have a team of hipsters who all know how it works, then it may be a fine choice. Otherwise I would probably recommend using something else.
I feel that Python is a bit of a ‘Microsoft Word’ of languages. Your own scripts are obviously completely fine, using a sensible and pragmatic selection of the language features in a robust fashion, but everyone else’s are absurd collections of hacks that fall to pieces at the first modification.
To an extent, ‘other people’s C++ / Bash scripts’ have the same problem. I’m usually okay with ‘other people’s Java’, which to me is one of the big selling points of the language - the slight wordiness and lack of ‘really stupid shit’ makes collaboration easier.
Now, a Python script that’s more than about two pages long? That makes me question its utility. The ‘duck typing’ everywhere makes any code that you can’t ‘keep in your head’ very difficult to reason about.
Frezik has a good answer for SQL.
In theory, Ansible should be used for creating ‘playbooks’ listing the packages and configuration files which are present on a server or collection of servers, and then ‘playing the playbook’ arranges it so that those servers exist and are configured as you specified. You shouldn’t really care how that is achieved; it is declarative.
However, in practice it has input, output, loops, conditional branching, and the ability to execute subtasks recursively. (In fact, it can quite difficult to stop people from using those features, since ‘declarative’ doesn’t necessarily come easily to everyone, and it makes for very messy config.) I think those are all the features required for Turing equivalence?
Being able to deploy a whole fleet of servers in a very straightfoward way comes as close to the ‘infinite memory’ requirement as any programming language can get, although you do need basically infinite money to do that on a cloud service.
No love for the ‘declarative’ programming paradigm? You can actually do some useful work with SQL or Ansible…
Not very easy, even then. Very pure water will absorb CO2 out of the air to make carbonates, it will strip ions from the surface of most materials you’d want a make a distillation column from. It’s a very aggressive solvent.
Well, we know that our understanding of physics isn’t correct - galaxies rotate faster than we think they ought to based on the amount of matter that we think is in them based on our theories of gravity and the evolution of the universe.
The “simplest” explanation is that there’s a particle that only interacts gravitationally, and has no other interaction with matter, hence being dark. Gravity might work differently on galactic scales, although it’s hard to make that maths work; or neutrinos (which are also ‘dark’) don’t have the gravitational interaction that we expect from theory.
Simple answer is that we don’t know, and “dark matter” is the useful placeholder term until we work it out. Could be a lot of things, although there’s a lot of things that we know it isn’t.
Wikipedia has a big list of all the things that don’t fit our current model, and which a proper theory of everything would have to explain. Dark matter ticks all the boxes, whereas other theories work for one or two but can’t explain the rest.
Yeah, swapped out grub for systemd-init on a running Arch system not too long ago. Arch is cool with it. Be sure not to make any really bad typos while you’ve not got a boot manager, of course.
As an aside, the Mars rovers are much larger than this - we don’t see them side-by-side with people for comparison very often. Curiosity is the size of a car - three metres on a side, two metres tall, and weighs the best part of a tonne.
A binary tree is one way of preparing data, usually for sorting. Each node can have a left, right, or both, children.
A
/ \
B C
/ \
D E
“Inverting the tree” means swapping the children for each node, so that the order that the nodes are visited is reversed. Depending on whether you want to copy the tree or swap it in place then the algorithm is different. C++ provides iterators too, so providing a “order reversed” iterator can be done efficiently as well.
You’re going to have to visit every node and do at least one swap for every node, and an efficient algorithm won’t do much more than that. Bring unable to do it suggests that the student programmer doesn’t understand stacks or recursion yet, so they’ve more to learn.
After having used Grub for about twenty years (eek) I was uncertain about the alternatives, but systemd-boot is absurdly better. Much better configuration, much better documentation, fixes a while pile of bugs that Grub team had as “won’t fix” for years and years. No reason to ever go back.
Your classic VGA setup will probably be connected to a CRT monitor, which among other things has zero lag, and therefore running your sound separately to your audio setup, which also has zero lag, will be fine. Audio and video are in sync.
HDMI cables will almost certainly be connected to a flatscreen of some kind. Monitors tend to have fairly low lag, but flatscreen TVs can be crazy. Some of them have “game” mode (or similar) but as for the rest, they might have half-a-second or more of image processing before actually displaying anything. Running sound separately will have a noticeable disconnect between audio and video; drives me crazy although some people don’t notice it. You would connect your audio setup to the TV rather than directly to source to correct this.
Now, the fact that a lot of cheap TVs only have a 3.5mm headphone jack to “send on the sound” is annoying to me, too. A lot of people just don’t care about how things sound and therefore it’s not a commercial priority. Optical digital audio output would be ideal, in that cheap audio circuitry inside the television won’t degrade the sound being passed over HDMI and you can use your own choice of DAC, but they can be both expensive and add a bit of lag as well.
TempleOS network edition.
True. I’d mentally envisioned it as a whole series of “bread powered water wheels” down the side of the building, with a furnace at the bottom. Nothing actually going fast enough for friction to matter. A machine that only tried to convert all the kinetic energy at the bottom would be wasteful, as you say.
Plainly, we’re going to have to put some engineering design time into the concept of this.
A kilogram of bread is about 2000 calories, about 9 kJ. Your body “burns” food too - probably more efficiently than you could make a steam engine for the same, but it’s about that much.
Energy from gravity is equal to mass * gravity acceleration * height. 1 kg of bread in a 9.81 m/s/s field has the same gravitational potential at “about a kilometer”.
If you’re throwing magic stake baguettes off the top of the Burj Khalifa, the energy would be about equal.
Bless her. If someone that really ‘loves and appreciates wine’ but ‘hates eggs’ finds that a complete nightmare, then I (who am the opposite) should leave it alone.
She’d absolutely cooked the shit out of those eggs, though. I’d probably hate them too if I only got ‘yellow cooked until it’s a powdery dust’ as my options.
Well yeah. You barely use groups on a personal machine - maybe once and done for audio and VMs, depending on what distro you use - and at work you’d automate that shit, probably have it centralised.
Filesystem-as-a-db is why MongoDB is webscale. You just turn it on and it scales right up.
I really like the book - I think it’s one of his best. Subtle ‘unreliable narrator’ mind-fuck from beginning to end, nicely written and characterised. The film of it is an abomination, though.