It's quite an old-fashioned word - you might find it in some classic literature. Less so online. Short for 'nincompoop', I think - both words mean a foolish and incompetent person.
- Posts
- 2
- Comments
- 378
- Joined
- 2 yr. ago
- Posts
- 2
- Comments
- 378
- Joined
- 2 yr. ago
Enough of that crazy talk - plainly
WheeledDeviceServiceFactoryBeanImplis 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.mincluttering 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...
I found that too. The animations are misleading - just listen for when you need to press the buttons.
- JumpDeleted
Permanently Deleted
The plural of faux pas is also faux pas, because you know, French. But this is less one false step in the dance, than doing entirely the wrong dance altogether.
- JumpDeleted
Permanently Deleted
Yeah, Fark used to be great. That bear headline is a beast.
And then they got rid of the 'foobies' (ie. nudity) links off of the main page in order to appeal to advertisers, then they got rid of lots of extra stuff that upset advertisers, then they started shadow-banning paying subscribers if their posts didn't fit the narrative. And then all the users got fed up of it all and moved ever to Reddit, where the mods were more transparent and there was more of a sense of community. How ironic.
If your core site content is users posting links and commenting on them, then there's probably a lesson to be learned about how important it is to treat your users well and have a welcoming, inclusive community. Probably a lesson that Lemmy users have already learned, mind.
Although you should give the egg to the thief (he can open it and you can't) and then kill him and retrieve it from his dead body later, otherwise you can't win the game. Obviously.
Broke my first one on the final boss of Sekiro, which can be quite intense in places. Bought another one immediately when they announced they weren't making them any more.
Hesitation is defeat. Although, wish I'd got three as well...
- JumpDeleted
Permanently Deleted
English does have some very good bits:
- easiest adjective declension rules of any language, ie. none.
- verb conjugation rules can be scribbled down in their essence on the back of a napkin and there's not that many exceptions; probably the easiest of any Indo-European language.
- no "grammatical" gender; only pronouns are changed for gender and they're mostly as expected from biology
- no polite vs. informal forms of "you" and rules to remember
- loads of words, for subtle nuance and meaning
...and some less good bits:
- loads of words, to confuse learners.
- the spelling rules are the fever dream of a madman. Many words are distinguished by stress, which is not marked. Want to learn the language by reading it? Ha ha no. Also, loads and loads of vowel sounds compared to most languages.
- massive reliance of "phrasal verbs", where the meaning can't be guessed from the parts. A "hang up" and a "hang over" have nothing to do with hanging and nothing to do with each other, despite up and over describing similar concepts
- grammatical concepts that don't exist in other languages, like "do support" for forming questions or negating a statement. Mood and tense of a sentence might be difficult to parse for some learners as that's indicated by "trigger words" rather than anything more concrete
- the native speakers do like to come out with some nonsense, too.
- JumpDeleted
Permanently Deleted
Alas no. Sur-rip-tish-yis-ly. Apparently you can blame Latin for sub + rapere = "secret snatch".
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.
CMake, which is kind of the universal standard build system for C++ now, has "fetch content" since v3.11. Put the URL of a repository (which can be remote, but also local, which is handy) and optionally the branch / commit ID that you'd like, and it will pull it into your build directory automatically. So yeah, you can pull anything nefarious that you'd like. I don't think most people would question pulling and building a library from Github as part of the build, especially if it had a sensible name for the task at hand.
You've got that a bit backwards. Integrated memory on a desktop computer is more "partitioned" than shared - there's a chunk for the CPU and a chunk for the GPU, and it's usually quite slow memory by the standards of graphics cards. The integrated memory on a console is completely shared, and very fast. The GPU works at its full speed, and the CPU is able to do a couple of things that are impossible to do with good performance on a desktop computer:
- load and manipulate models which are then directly accessible by the GPU. When loading models, there's no need to read them from disk into the CPU memory and then copy them onto the GPU - they're just loaded and accessible.
- manipulate the frame buffer using the CPU. Often used for tone mapping and things like that, and a nightmare for emulator writers. Something like RPCS3 emulating Dark Souls has to turn this off; a real PS3 can just read and adjust the output using the CPU with no frame hit, but a desktop would need to copy the frame from the GPU to main memory, adjust it, and copy it back, which would kill performance.
Which is ironic, because Fallout 4 is the game that caused me to no longer be hyped for anything else that Bethesda had coming. Fallout 76 and Starfield didn't disappoint, because I was expecting them to be shit from a company that had lost its way, and they delivered spectacularly.