shortercode
They have some cool advantages. Like being able to read directly from the archive without decompressing the whole thing, per file checksum, and skipping compression on parts which won’t benefit. You can also wedge large amounts of arbitrary data into the file without changing it which… is kinda weird and sometimes useful?
Nasty bits are they used 32 bit ints all over the place, so rely on hacks to support larger files. Can’t support true streaming decompression. Implementations can vary quite a lot, as can compatibility. They also have a number of old and weird features that people don’t really use. Like being able to split a zip file into multiple parts, some ancient compression techniques etc.
Defer only cares if the variable leaves scope. At the end they mention the new “using” syntax which only requires you to mark the declaration, not requiring an additional statement for the cleanup. It’s kinda nice but the resource needs to implement a cleanup method making it less flexible than defer.
Idea was a DSL that could be loaded into a JS runtime, then fed data streams. Your module would transform that data into various output streams which could then be fed to a separate reporting library. Powering dynamic reports based on a template.
Our first iteration was already pretty powerful but I had some big plans to bring it into a more JS feeling syntax to reduce complexity.
I think there was a case of Teslas having these sorts of failures at one point due to them writing logs quite aggressively.
Another example was MacOS causing rapid wear due to virtual memory swaps if I recall on devices with smaller amounts of RAM.
Thankfully these days she can get herself to sleep. But I miss it sometimes
I saw a sibling comment mentioning about the drop curbs making the path awkwardly angled. Yeah they can be a real pain. Pushing a pram along on an angled path is hell on the wrists. But a lot of the troublesome ones are the wider ones for people to get their cars up to their front door.
Makes you think about how hard just going down the road with a wheelchair is.
Firstly if an app does want a space that’s filesystem shape but does not want users/apps to have access for security or consistency reasons ( think Spotify offline storage of songs ).
Secondly if the user has access they can do the “easy” thing and just throw lots of files in, including things which are sensitive anyway.
It’s interesting to look at how Android and iOS have handled filesystem sandboxing in relation to this.
I think the WebKit take on this is good and a better fit for most apps. They instead implemented Origin Private File System. Which is based on the same API bits but the folder is only accessible by the website. The downside is the user loses some control over the files:
- can’t see what’s being stored
- can’t easily backup those files
- has to use that web app to access the files
- usual nonsense about important files being classed as “cookies” or some nonsense by cache cleaning tools, leading to users deleting their data without realising it
In the style of Sauron I’m channeling all my frustration and hatred of slow loading tools that require you to pay a subscription, buy the digital book on every platform you want to use it on, and won’t let you use the physical book from your shelf.
For my first pass I decided on focusing on a character creator for a single game and streamlining the process.
I started with the 5.5e SRD but got frustrated with the sheer amount of text without much actual content ( 100+ A4 double column pages of spells, only 1 subclass per class ). Plus a number of weird and frustrating rules that make it hard to create software for. As I’m using Nimble RPG at the table a bit recently and it has a much nicer license I’ve switched to that and been getting on a lot better. Character creation is almost done and I’be moved to character sheets and persistent object storage now. This is the first major project I’ve done with sveltekit and I’m really enjoying it.
For me HN became a lot less interesting when AI became popular. I don’t want to read about OpenAI’s incremental improvements, or see an AI generated landing page that fails to tell me what a project is about. Maybe the people who love the craft have also reduced the amount they are writing…
Concerns about age gating etc are true but as we’re already experiencing that nonsense without social media bans it’s kind of a moot point.
Now function colouring is interesting but not for the reason these articles get excited. Recolouring is easy and has basically no impact on code maintenance. BUT if you need that code path to really fly then marking it as async is a killer, as all those tiny little promises add tiny delays in the form of many tasks. Which add up to performance problems on hot code paths. This is particularly frustrating if functions are sometimes async, like lazy loaders or similar cache things. To get around this you can either use callbacks instead or use selective promise chaining to only use promises when you get a promise. Both strategies can be messy and trip up people who don’t understand these careful design decisions.
One other fun thing is indexeddb plays terribly with promises, as it uses a “transactions close at end of task” mechanism, making certain common patterns impossible with promises due to how they behave with the task system. Although some API designers have come up with ways around this to give you promise interfaces for databases. Normally by using callbacks internally and only doing one operation per transaction.
District based heating is generally much more efficient than per building heating, and this side steps many of the issues that you would have installing/maintaining servers on your property.
Honestly my only concern is the impact of having a data centre nearby. They are asking for people to put a deposit down for the heating. I won’t encourage it, but I will make use of it if they put it in!
I hate this philosophy. But it’s seems to be the preferred path for Microsoft.
But instead we’ve found a way to circumvent the process. Losing the understanding of your own problem and the new ideas that come off the back of it.
I’m reminded of the story that NASA had a research project to make pens that would work in space, and Roscosmos just used pencils. I always thought NASA came off worse in that anecdote, but I wonder what they learnt while making the pen…
Then of course we produced it at industrial scale for decades flooding the entire planet with this stuff.
- Put your child on the potty during changes, and first thing in the morning. Build’s association and encourages bladder control. Do this long before trying to get them out of nappies.
- Reusable wipes are also a massive win. We have face wipes and bum wipes, basically just soft cotton. Bit of water under a tap and your good.
- Our biggest hurdle for moving away from nappies was nursery, as they wouldn’t consistently put a younger toddler on a potty.
- Introducing a potty earlier means less poopy nappies, turns out even a toddler dislikes pooping their pants.
- Expect a stupid amount of laundry, and the nappies to leak a bit ( so more laundry ). You also can’t use a drier with them as it damages the water proofing layer.
- Travelling is harder… Used nappies should be cleaned within 3 days, so expect to take dirty nappies away with you for washing plus clean nappies/boosters/cloths/bags.
- It’s easy to buy new/almost new/good condition second hand. Either people want to do it but don’t get on with it, or never start, or potty trained. Means a significant reduction in cost. But expect ones that have been used less to be more water proof and Velcro to work better etc.
- Our daughter loved playing with the clean ones, putting them on toys, using cloths etc. Probably helps they have cool designs on the outside. I expect a disposable wouldn’t work well after it had been played with.
- If you need to use disposables while you’re away etc the chemicals can cause rashes after your child has adjusted to their absence.
- When they start weaning you have to “remove the solids” before washing. Yes this is unpleasant, but more often than not is just upending it over toilet. You get used to it. Same as nappy changes in general and washing nappies.
- When we did swap to pants we didn’t do anything special. Just stop nappies, ensure you have a potty nearby, and deal with it for a few days. It’s uncomfortable for them and they learn fast. Expect a bit of frustration and wanting the old routine back.
I dislike the “you can change the syntax” argument because that just doesn’t happen. Closest thing is a new language that compiles to another.
That being said while I don’t struggle much with the glare from oncoming headlights I find that visibility beyond the oncoming vehicle can be severely limited by the bright light. This often causes me to slow down and squint to be careful of any dangers beyond the vehicle.
Despite all this I think it’s still a move in the right direction.
The only “big” local first app I’m aware of is Linear.
So yeah entirely unsurprised that people aren’t engaging with science on X