HNHacker News
TopNewBestAskShowJobs

radiowave

875 karma · joined December 12, 2010

submissionscomments
radiowave··on Logica, a novel open-source logic programming language
None of those things (views, stored procs, functions) are part of the query language. They all involve making somewhat permanent alterations to the structure of the database, and are entirely capable of conflicting with other objects in the database. So if your query needs these things, you're now into "release management" territory.

In terms of lack of linguistic abstraction, try writing a query that abstracts over what table it's to be run against, allowing choice of source data to be parameterized, without either resorting to shenanigans like passing strings of SQL fragments around to be eval'd during query execution, or writing the query in some other system such that it can then be compiled into SQL for execution.

radiowave··on 1984: The Hitchhiker's Guide to the Galaxy
take all

put all in thing

radiowave··on Running a Bakery on Emacs and PostgreSQL (2019)
Indeed, though his work-around of adding a path column is something is worth having anyway, because it makes it much easier to see where the generated output has come from.
radiowave··on Squeak: A Free Smalltalk System – On RISC OS
Looks like the Squeak VM site doesn't currently like "www" - hence the download link should be:

http://squeakvm.org/riscos/

radiowave··on AirPods Max: An Audiophile Review
SoundOnSound have a good article covering why this doesn't happen. In short, there's no standardized methodology (i.e. standard dummy head) for measuring it, and the interactions between the headphones and the listener's head vary significantly.

You could (relatively) easily measure the free-field response of the headphones, but I suspect that would tell you very little about how they will sound when you're actually wearing them. For example it would likely underrepresent the difference between closed-back and open-back designs.

https://www.soundonsound.com/techniques/designing-measuring-...

radiowave··on Show HN: Fourhands is a P2P MIDI jam room for pianists
Given that MIDI expects 100% reliable delivery, I'm curious to know if there's any special technique used here to prevent (e.g.) intermittent packet loss causing stuck notes.
radiowave··on Plotting patterns in music with a fantasy record player
I don't follow you. The musical pattern repeats over a fixed length of time, and the turntable completes one rotation within the same length of time. How would that produce a faster rhythm in the innermost rings, absent a spiral?
radiowave··on Minimal safe Bash script template
I tend to apply much the same rule as emptyparadise - once conditional logic appears, it's time for a rethink. Part of my rationale for this is that I assume that I'm dealing with the thin end of the wedge - if there's enough complexity in the task to warrant conditionals, there's likely a whole bunch more (or there will be in future) that I haven't encountered or grasped yet.

I'm thus willing to take the time-hit on rewriting in Python, because I'm betting that resulting code will be easier to adapt and easier to troubleshoot as this extra complexity gradually comes into view.

radiowave··on Babelfish: SQL Server-to-Postgres Translation Layer
My guess would be: by not using Postgres's money type.
radiowave··on An Introduction to ZFS
> Maybe a small recordsize can have some benefits when overwriting parts of the files...mmmhhh...?

Right. People who've done more testing than me reckon on 16KB being a good record size for transaction-processing database work, where tables are seeing lots of small inserts and updates. (You might think matching the database's block size would be ideal, e.g. Postgres writes 8KB at a time, but the rationale here is that you tend to get better compression at 16KB recordsize than 8KB, and the benefit from this outweights the write-amplification.)

But if database update performance isn't a big deal for you then you can probably just ignore this.

I've not done any testing of my own at the 1MB size, but I don't think I'd be inclined to try it unless I was fairly confident that there weren't going to be many small writes to big files.

In short: use the large recordsize where you think you've got a good case for it, and likewise with a small record size. Otherwise, just stick with the default.

radiowave··on Herman Mankiewicz, Pauline Kael, and the Battle over “Citizen Kane”
I'd guess the way in which a persons screen-writing job normally concludes doesn't involve either quitting or being fired.
radiowave··on A Short Story About SQL’s Biggest Rival
Yes, but it's extremely clunky. The number of times I've had to write out a whole chain of CTEs just because I wanted to apply one window function to the output of another.

In which context, "compostable" is a fantastic Freudian typo.

radiowave··on Database Version Control with Liquibase
Yes. If you're using XML with Liquibase, it's definitely worth using an editor that supports XML schemas for autocomplete and validation as you type.
radiowave··on Home Studio Setup Costs Compared – 1980s And Now
This only works if you either have a guarantee that everyone else is also going to listen to your work on headphones, or total disregard for anyone who isn't.

If you expect people to listen to it on speakers, you need to listen to it on speakers.

radiowave··on Home Studio Setup Costs Compared – 1980s And Now
I bet the plugin version doesn't introduce buzz on single-coil pickups, either.
radiowave··on Home Studio Setup Costs Compared – 1980s And Now
The trade-off is that sample rate conversion introduced its own artefacts, though we have much better algorithms (and of course more CPU power) for it today.

I'm not sure that aliasing was in itself a big problem, you're perhaps refering more to the audio artefacts introduced by the anti-aliasing filter. But in any case this wasn't even the biggest problem with converters back then. IME, quantization distortion was a much bigger issue. You had to watch the signal levels really carefully - too loud and you'd get absolutely brutal distortion (sometimes including wrap-around, where the value reported by the A/D converter goes instantly from maximum value to minimum value), too quiet and everything turns into a grainy-sounding mush.

The world changed in the early 90s when delta-sigma (aka "oversampling") converters came along, pretty much solved all these issues, and so allowed the price of decent converters to steadily fall, as normal semiconductor manufacturing economics kick in.

radiowave··on Automatic SSL Certificates for internal IP's for home k8 setup using LetsEncrypt
In which case it may be advisable to delegate the acme-challenge record to a different DNS provider, if doing so allows you to sidestep the anycast issues.
radiowave··on OpenZFS Merged to FreeBSD
Likewise. Been using ZFS for over 10 years. Been through intermittent controller faults, backplane faults, cabling faults on a variety of ZFS, ext, and NTFS systems.

The one time I lost data from a ZFS system (which was a faulty controller silently writing garbage to multiple disks in the array), ZFS told me exactly which few files were uncorrectable, and I was able to restore them from backup.

Not one single second of doubt as to which storage system I want my data on.

radiowave··on OpenZFS Merged to FreeBSD
I don't mean to be criticizing your choices, but I'll note here that if you're willing to avoid enabling the latest and greatest ZFS features, bringing up a machine that can mount your disks can be as simple as booting from Ubuntu install media, and having internet available so you can run "apt install zfsutils-linux".

(And somebody's probably going to correct my ignorance and point out that beyond some release 'x', the ZFS stuff is already built-in.)

radiowave··on How to Write in Plain English
Of course, FAQs originated in places like mailing lists and usenet groups, where it's arguably a good fit, precisely because there is no real standing body of text. The trouble is that it then got shoe-horned into being used on websites.
radiowave··on TruffleSqueak: Polyglot Programming with Squeak/Smalltalk and GraalVM
One of the problems with attempting to propagate Smalltalk culture is that when your interaction with the machine doesn't resemble interacting with a teleprinter, then a wall of text becomes a poor medium for capturing it.

Not disputing that video brings its own problems.

radiowave··on Expository Programming (2006)
A similar sentiment to Alan Kay's notion that "The computer revolution hasn't happened yet."
radiowave··on Show HN: TinyPilot – Build a KVM over IP using a Raspberry Pi
From memory, this is correct. It's only the USB-C port that allows OTG operation. I remember a while back seeing someone selling a special splitter cable for the rpi4 which provided 2 separate USB connectors, one for powering the rpi and one for attaching the pi as a gadget to a USB host port. But I can't remember where I saw it, and haven't been able to turn up a link to it.
radiowave··on Databricks acquires Redash
OTOH, I've evaluated Metabase a number of times and never manage to get more than 10 minutes in before running into some staggering flaw that convinces me that I can't put this in front of other people in the business and expect them to use it. I ended up deploying Redash instead - it is unquestionably a much less ambitious project, but it mostly achieves its aims.
radiowave··on Computational Music Synthesis
How did I not know about Edisyn? The Microwave XT will be getting an outing this evening, I think. Thanks.
radiowave··on Who the Hell Is This Joyce (1928)
Thank you. This is a much clearer explanation than I was likely to give.

I'll add that there was some also implied humour in my comment, and perhaps also in Wells's remarks to Joyce. Humour is the great leveller, before which we all have to confront our failures and fallibilities, and laugh.

radiowave··on Who the Hell Is This Joyce (1928)
> Plus it's terrible to tell a friend that you may both be wrong

You're very definitely not British.

radiowave··on Design Principles Behind Smalltalk (1981)
Smalltalk prizes interactivity, in the manner that arises from being able to make small, incremental adjustments to code while it (and it's state) remain in memory.

Its rejection of static typing is not axiomatic, merely an expedient way of achieving those interactivity goals. Could the two things be reconciled? I don't know, but I think at least that it shouldn't be unthinkable.

As an aside, static type systems which can be mutated during runtime are astonishingly commonplace. They're very crude, and tend to be called "relational databases", and doing those mutations is a major pain because in spite of all that's elegant about relational algebra, actual SQL is a fucking abomination. (And this is coming from a full-on Postgres fanboy.)

On your comment about the similarity of Ruby, I know what you mean, and yet I regard Ruby as being basically nothing at all like Smalltalk. That's because I'm principally thinking in terms of the development culture, tools, and working practices, and not thinking in terms of the implementation of the VM or the object model, or the names of certain methods.

So similarity between languages is a tricky thing to nail down, not least because in the case of a gestalt system like Smalltalk, "programming language" is actually a tricky thing to nail down.

radiowave··on Design Principles Behind Smalltalk (1981)
Ah, you mean like a version of Python that everyone can agree on!

Joking aside, it's an entirely understandable sentiment, but Smalltalk is not only an old language, but also one that lives in a symbiotic relationship with its tools (which defy the normal notions of language standardisation).

As things stand, if you want a standard, what you're likely to get is a time-capsule. Pharo in particular does not want to be a time-capsule, and while it's certainly been a source of frustration to me that Pharo has existed in such a state of flux for so much of its life, I understand that the change is necessary, and I remain cautiously hopefuly about the direction they're taking.

I'm not a daily user of Pharo, so while I have a rough idea that it is becomming more settled as time passes, I'm not an authority here.

radiowave··on The Rise and Fall of Commercial Smalltalk
I imagine they meant it in the sense of "entering a new age".
← PreviousPage 4 of 14Next →