I'm still trying to make 'sloppers' happen. Perfectly describes the lack of thought that goes into what they produce.
- Posts
- 1
- Comments
- 248
- Joined
- 3 yr. ago
- Posts
- 1
- Comments
- 248
- Joined
- 3 yr. ago
The ability to do some basic calculations is what was missing in CSS from the start, IMHO. You don't want paragraph text to be too narrow or too wide as it would become unreadable, so a rule like "at least 20 ems, and then whichever is smaller of 100% or 80 ems centered on the page". But that required either really convoluted layout and rules, or just to work it out with JS after the page is loaded.
Would have been even better if we'd got Donald Knuth involved in the early CSS efforts, with some LaTeX-like attention to the details. There's no reason that computers can't render beautiful text, but it's rare for one person to be an expert typesetter and an expert programmer.
You can turn off "delete", but modification is a danger, it's true.
Turning off delete makes it excellent for eg. backing up photographs on your phone. I've got it doing this from my Android to my raspberry pi, which puts them on my NAS for me. Saves losing all my pictures if I lose my phone.
Think if the GNU project had spent less time working on 'clever' recursive acronyms and fitting Scheme into everything, and more time hacking, we might actually be using their kernel.
Linus locked himself in his bedroom for the summer and got almost all of POSIX working on 386. That's the level of geek to aspire to. If RMS had just decided to name his kernel after himself rather than messing, we'd all be be using Stallix instead.
The 'traditional' way of storing a database is on a mainframe or supercomputer, where all the information is stored in tables with the information all uniquely stored, frequently containing id references to other tables. For instance, an 'orders' table would have a customer id in it, and the 'customer' table would have their name and address. The programming language for databases like that is SQL - PostGres and Oracle are examples. That model gives you a lot of advantages - the data is always consistent, changes are either made completely or not at all - but every query has to go through one machine, so performance can suck, and you waste a lot of time 'joining' tables together for certain kinds of query.
If you're storing eg. a blog with comments on it, that model doesn't make sense. Each page has a varied selection of comments, comment will have a username and maybe their icon, which will rarely change, but will need to be evaluated by the database every time. It would make more sense to output the pre-rendered page as a JSON blob, and you could have a hundred machines with a few pages each to share the load. Updating people's icons and adding new comments would need to be done by telling each machine to make a certain update if they've a copy of that page; you'd 'eventually' be consistent, but if you don't care about that then you get a very scalable robust solution quite cheaply. Examples of such 'NoSQL' databases are MongoDB, Hadoop and DocumentDB.
Linux foundation have looked at DocumentDB's license and said 'yes, free enough for us', so they'll adopt it.
What you can achieve in a couple of pages of Python can be pretty spectacular. It's also mostly very easy-to-read, with the possible exception of class inheritance, which is confusing mess.
If you need to write more than a couple of pages, then its lack of types becomes a hindrance to me - doing refactors when functions can take basically any arguments is quite painful, for instance. Not requiring any particular structure is great, up until you start to struggle with lack of structure.
Ideal programming language for when you're wanting to do something that would be a bit too unwieldy for a shell script. It also makes network requests and json parsing very straightforward, so it's great for interacting with REST APIs and writing simple microservices. Fast to write and runs quite quickly, so a good choice for Advent Of Code-like tasks. Would probably choose a different language for larger projects or when working in a team, though.
Yeah, some of the answers it produces are very questionable. The implementation of a lot of the stat functions is super-naive and not very stable in borderline cases. Take the standard deviation of three identical numbers, get an answer which is nearly-but-not-quite zero. They've also refused to improve their algorithms as it might break existing customer worksheets.
- JumpDeleted
Permanently Deleted
Visited a traditional water-powered flour mill recently. Very cool, beautiful building, and the end product makes really delicious bread and pasta. Wholemeal, not too fine, nothing in it but grain. Perfection.
From the water flow, drop and wheel turning rate, I made the maximum possible power as about 5 kW. Probably optimistic to think you'd get a quarter of that in practice. Still, that's a huge amount compared to what a person can produce, and it's 'on tap' 24 hours a day. That kind of thing does explain why, in the days before electrification, that having 'the right landscape' made some areas really wealthy and some others not. Exploitable renewable energy, what a concept.
So yeah, your proposed map would be really interesting. The Romans burned down whole forests to make steel - you simply couldn't refine it in a place without. It would be fascinating to see the map of "power resources" and the resulting industries, even if it would be very hypothetical.
A CD with RedHat on it? Pretty fancy. My first RH installation came on about three boxes of floppy disks, took hours to unpack it all. And damn right, been all uphill since.
That's why I like make basic grammatical mistakes, speling erors, and include a few fucks in my internet writing. Nobody's not gona mistake me for no got dagned robot.
Strange, it has the 'autoplay more like this' option on the web player (which does basically the same) but not the explicit 'artist radio' option. Huh.
"Go to Radio" on the app. Hmm...
Aww. We buried our old cat's ashes at the spot in the garden where he loved to sit and watch the world - a shady spot under the rhubarb. It's where new cat loves to sit as well.
I'm not sure that they're even going to be useful for gamers. Datacenter GPUs require a substantial external cooling solution to stop them from just melting. Believe NVidia's new stuff is liquid-only, so even if you've got an HVAC next to your l33t gaming PC, that won't be sufficient.
They have the human made ones, they have the "artist radio" function that plays songs similar to a band you like, they have a weekly top 30 based on stuff you've been listening to. The headline 'albums of the week' are based on what they like, which I don't think is unfair - I've really enjoyed some of them.
I listen to a lot of metal and electronic, and I've always found the descriptions excellent - usually several paragraphs even for the most obscure of bands. Was well impressed that they had Lambrini Girls as one of their 'albums of the week', and their album at studio quality. Not that that's essential for punk. Admittedly I don't listen to a lot of indy, but they've always had what I've wanted to listen to.
My main complaint about the UX is that it's nearly identical to Spotify, but I suppose there's not much else you can do. Something particular about it that you dislike?
Yeah, the web client works just fine on Linux. A good native client would be better, of course, but I'd rather use the web one than a half-assed native one.
Just saying; cancelling Spotify and changing to Qobuz takes five minutes. Sound quality is amazingly better, the curated recommendations are done by human beings that love music, and 'just works' with everything that Spotify does. (For us, anyway.) It's French, rather than Norwegian-American like Tidal is, if you're trying to stop spending money on everything US at the moment, too.
Yeah, we have that with our customers sometimes. To me, an app should either be running full whack - maxing out bandwidth on CPU, disk, memory or network - or completely idle. Chuntering along at 2% is a bug. For the ones that put 'monitoring tools' that raise errors when we reach 100% on something, we set a Linux CGroup to throttle the offending resource. Takes longer, obviously, but not worth arguing with their network deployment teams 🤷 .
I learned z80 assembly back when the cutting edge of technology was a ZX Spectrum, and 68k assembly when I upgraded to an Amiga. That knowledge served me quite well for my early career in industrial automation - it was hard real-time coding on eZ80's and 65c02 processors, but the knowledge transfers.
Back in the day, when input got mapped straight into a memory location and the display output was another memory location, then assembly seems like magic. Read the byte they corresponds to the right-hand middle row of the keyboard, check if a certain bit is set in that byte, therefore a key is held down. Call your subroutine that copies a sequence of bytes into a known location. Boom, pressing a key updates the screen. Awesome.
Modern assembly (x64 and the like) has masses of rules about pointer alignment for the stacks, which you do so often you might as well write a macro for it. Since the OS doesn't let you write system memory any more (a good thing) then you need to make system calls and call library functions to do the same thing. You do that so often that you might as well write a macro for that as well. Boom, now your assembly looks almost exactly like C. Might as well learn that instead.
In fact, that's almost the purpose of C - a more readable, somewhat portable assembly language. Experienced C developers will know which sequence of opcodes they'd expect from any language construction. It's quite a simple mapping in that regard.
It's handy to know a little assembly occasionally, but unless you're writing eg. crypto implementations, which must take the exact same time and power to execute regardless of the input, then it's impractical for almost any purpose nowadays.
Doggy paddle is not a very efficient stroke. When will cats learn?