I think this may be a register (https://en.wikipedia.org/wiki/Register_%28sociolinguistics%2...)
1,152 karma · joined December 4, 2018
I think this may be a register (https://en.wikipedia.org/wiki/Register_%28sociolinguistics%2...)
Any thoughts from biologists?
Maybe I can - they're asking for the moon, and a pony?
I see job ads that as for advanced mssql with SSIS/SSRS/SSAS data analysis, good c# and/or python, some web framework, powershell, some visualisation tools, some no-sql db experience[0] and often big data frameworks (hadoop, spark) on top ("and some knowledge of statistics and data analysis would be helpful!"). And OO, and FP. And they often ask for domain knowledge on top.
(edit: and I forgot, they often want data warehousing as well).
I think some of these are just added by clueless HR drones to pad job ads out (some of HR really are clueless).
[0] why ask for SQL & no-sql?
Parasite the korean film?
Perhaps related, perhaps not, I never 'sink in' to films I'm watching. My old GF seemed to be able to, but I'm always on the outside looking in, never immersed. I wonder if that's linked.
It's (IIRC!) something to do with the situation of
select x + y as x
from ...
group by x
which x are we talking about? (Logically that example is crap because only the alias x makes sense, but something like that anyway).sorry!
Found it (thanks google): https://news.ycombinator.com/item?id=20591621 Simplicity was staring me in the face, it took weeks to find it.
Well, no. Complexity has an obvious price but simplicity does too. You have to work for simplicity, even fight for it. Think of code; it just somehow becomes more complex. You have to work to pare it back to what's needed.
I can't think ATM of better examples (and you deserve some), but no, simplicity does not come easy.
A nice phrase I came across: "elegance is refusal".
I seriously take issue with "Reference Column Position in GROUP BY and ORDER BY" though. If it is restricted to ad-hoc (AKA messing-about) queries I'd be fine with it, but it won't be. Just don't do it.
"Selective citations of the literature allow Lomborg to make statements that are correct but unrepresentative of the best, full state of environmental scientific knowledge"
"Yet his [lomborg's] critics are rarely attacking the facts in his citations per se; they fault what Lomborg does with them and, of course, his neglect of more relevant citations elsewhere."
Anyway, that's SA's side. Follow the link to find more. Caveats: this was years ago, and the quotes above are my selection, which you may consider one-sided.
"were"? I don't know.
I don't remember any particular tooling, and the language was crap (Meyer was better at hype than language/compiler design).
IIRC sather was eiffel with the subtyping holes fixed. Bertrand Meyer allowed holes in eiffel subtyping (which sather disallowed) which he (meyer) was sure he could deal with, but eventually they proved intractable IIRC.
My boss eventually abandoned eiffel, and let the eiffel company know why. It was not an enjoyable experience for either me nor him.
Performance was avoidably bad in some parts of the libraries.
I recall a major rewrite of some product being started then killed because performance sucked (surely much better now, but things took far too long to change).
Memory behaviour was not fixed until java 5:
"The original Java memory model, developed in 1995, was widely perceived as broken, preventing many runtime optimizations and not providing strong enough guarantees for code safety"
(https://en.wikipedia.org/wiki/Java_memory_model)
I'd also like to add Brinch Hansen's heartfelt lament
"If programmers no longer see the need for interference control [in java's threading] then I have apparently wasted my most creative years developing rigorous concepts which have now been compromised or abandoned by programmers"
Per Brinch Hansen, Java's Insecure Parallelism - SIGPLAN Notices, April 1999
> statically typed
with type holes for arrays
> with much simpler semantics
yep, too simple. IMO it relied too much on the programmer. Generics took too long to appear also.
> Unicode support
Broken cos they didn't read the spec properly. It has problem with the BOM on UTF8 which has bitten me (can't remember the details, think it was this https://stackoverflow.com/questions/1835430/byte-order-mark-...)
The advertising budget was what drove things, not common sense. Java could have been good but it was designed badly and badly oversold.
Tech is fad driven - look at all the big data projects by companies that don't need them.