Similarly, if the notification has a "Reply" option (say a Slack message), can you reply on your watch? Very useful when I get a work message when I'm walking the dog.
2,475 karma · joined November 9, 2009
Similarly, if the notification has a "Reply" option (say a Slack message), can you reply on your watch? Very useful when I get a work message when I'm walking the dog.
When Apple Music launched it was around the time that 3rd party apps were allowed to hook into Siri - so you could say "Hey Siri, tell MyToDoApp to remind me to do X in six hours" and MyToDoApp would add the reminder.
But it was only allowed for certain categories of app (strangely enough, categories where Apple didn't have a paid service). It wasn't permitted for music apps until a few years later, by which time Apple Music was established.
Similarly - when I connect my iPhone to my car over Bluetooth or wired connection[1] - with Spotify I get the normal play/pause/skip controls. But I can't see the upcoming play-queue, nor browse my playlists through the car's interface. If I listen through Apple Music, I can see not only my queue, playlists, albums and artists but also podcasts from the totally separate Apple Podcasts app.
Of course, the car interface is shite, but why can Apple's app do this and the third party not? Is it just that Spotify didn't bother implementing the relevant APIs or because those APIs were not available?
As a long-time Apple fan, my distrust of them is so great at the moment, I suspect the latter.
[1] The inbuilt head-unit doesn't do CarPlay, but I have a standalone wireless CarPlay screen. I like to connect the phone through Bluetooth (or wired) so the display unit shows my apps but I can adjust the volume and skip tracks using the steering wheel controls.
I'd say this is the point.
If it's "published as part of Obsidian" it implies Obsidian can break it at any time and the interop anyone else has built will need updating. But "published as a standalone spec" means Obsidian is saying "we won't change this without warning" (at the very least).
I put in a very random guess as to the points value of each request - nothing more than "trivial, easy, difficult, bastard-bloody-hell-shit-buckets-difficult".
I had Tracker set to work in "weekly sprints" - but they're not really sprints at all - it's just a unit of measure. Internally it averages the number of points completed over the last three weeks, uses that for an average velocity, then moves the date markers on the "backlog" list to match.
Then, when a client asked when something will be done, I could pretty accurately say "unless something urgent crops up, it will be '18th-24th March'" (where "something urgent crops up" means I insert a story at the top of the queue instead of at the end).
I got him to buy a Mac and for a few years things went well. But then he started complaining about it behaving weirdly or running slowly. I'd take a look and find he'd installed some free utility or some other odd bit of software that was screwing up his machine. I kept explaining why this happened and he never changed his behaviour.
I keep telling him to get an iPad, as at least then everything would be sandboxed and iOS would kill background tasks. But he says, no, he needs a real computer.
It allows me to leave my MacStudio at the office and work from a lower powered laptop at home (using Tailscale to connect) and everything feels like it’s running locally (it seems to run a service on the remote machine that indexes your files so the fuzzy file opener and full project search feel as fast as if they were running locally).
I have tried CodeServer on the remote machine (VSCode open-source in a browser) but that seems to get random pauses (presumably GC or something like that).
If anyone knows of something similar available outside of VSCode I’d love to hear about it.
That's also my go-to karaoke song (no codpiece unfortunately)
There was all that stuff about "connecting" (where you could send doodles and heartbeats to your Apple Watch wearing friends) and they made a big deal about watch apps and notification management. And of course the "luxury watch" aspect (gold watches that go out of date in a couple of years - sheesh).
It's only after a couple of iterations that Apple doubled down on the fitness side of things.
The olden days equivalent of the HN crowd (Slashdot? Kuro5hin?) hated Microsoft's behaviour but had to build on their platforms because there wasn't an alternative that would pay the bills. So Microsoft kept raking in profits and probably thought that everything was OK and there wasn't an issue.
But that ill-feeling meant that as soon as an alternative emerged (in this case Apple, powered by open-source, Unix, the web - and later smartphones with the iPhone and Android) there was an exodus and Microsoft's attempts to regain ground (IIS, Windows Phone) were widely ignored.
Apple is on the same ground now (and I say this as an Apple-lover). They are pulling in huge amounts of money through their behaviour but I have no doubt, as soon as an alternative appears (probably through some platform shift) they will come to regret it.
UPDATE: and it would be ironic if the Vision Pro was the thing that triggered the platform shift. If the Vision Pro works well as a Mac alternative (a proper productivity environment but with an infinite screen), once others implement the same idea effectively (and maybe not quite as well as Apple has) it could be the catalyst for developers (and hence apps) jumping ship.
Bootstrap basically takes standard elements and when you add CSS classes and data properties, it styles them and adds some JS behaviours.
Shoelace builds HTML custom elements, using CSS variables for controlling the style, with the JS baked into the custom-element code. And Shoelace uses the shadow DOM, so any customisations do not "leak" outside of your components (although this has its own implications).
Custom elements basically do the same as React/Vue/whatever (reactive properties, slots etc) but in a manner that's built into the HTML spec and into all browsers. (React/Vue et al also have mechanisms for building your components as custom-elements, but you're then adding the dependency on React/Vue when you reuse them - although Shoelace has a dependency on lit.dev, as the actual custom-elements spec is quite low-level).
But Bootstrap and Shoelace are essentially solving the same problem - a reusable design system - but Shoelace does it in a way that's already built in to browsers and arguably cleaner to use.
I read somewhere that Windows 98 sold 15 million licences. Add in OEM machines and you've got a base of computer users in maybe the 100-200 million range - most of whom either had to use the device for work (which meant training) or had a level of enthusiasm for computing (which meant self-learning).
Today there are 7-odd billion smartphones out there. Most users just want something that gets things done with as little friction as possible.
Who uses these things and how they use them has changed beyond all recognition.
It implies that teaching isn't a skill of its own. Some of the best football coaches were mediocre players (Alex Ferguson, Jose Mourinho) and some of the best players turned out to be very poor coaches (Steven Gerrard springs to mind at the moment). Can you only learn physics from someone who has made a world-changing discovery, or learn to write from a best-selling author? Or do you learn from someone who knows just enough to guide you in the right direction with enthusiasm and correct your mistakes in a way that doesn't make you feel like a failure?
What is correct is dogma in software development is a problem - software is too malleable and the world changes too fast to allow one set of ideas to dominate everything. That lesson hadn't even been thought about in the 90s though.
Mine is the M1-with-touchbar (same design as the intel version) which was released at the same time as the M1 MacBook Air - late 2020.
Slight tangent - even though the MBP has been struggling to handle my dev work (partly because the codebase I'm working on has grown significantly in the last two years) I won't be upgrading. Work bought me a MacStudio (M2 Max), which mainly runs headlessly on my desk (also running Homebridge and plugged into my big speakers for AirPlay). This means I'm keeping the MBP as my portable machine (using VSCode's remote extensions and/or CodeServer to do dev work from wherever). I also have a late-2015 27" iMac at the office (with OpenCore Legacy Patcher so it can run whatever the latest macOS is called nowadays). This also works perfectly well now all the hard stuff is done on the MacStudio - and the screen is still lovely. (My previous 27" iMac was in active service for 10 years, although it was almost unusable towards the end).
Another tangent - I bet that's why they're not doing the larger "pro" iMacs. If it weren't for VSCode Remote Extensions and OCLP, I would have ended up with a beautiful monitor that was essentially useless (as was my original 27" iMac). People who need that extra power should probably avoid all-in-ones and I won't be getting one again.
But for most people, who tend to have a single machine, a comparison to the 3 year old equivalent seems pretty fair to me.
If they were Epic, not Bandcamp, employees then Songtradr would be within their rights to proceed as they have. But Epic would have had to go through a redundancy process (including explaining why it's happening, detailing the alternative tactics they have explored and trying to find other roles within the organisation for the affected employees).
Of course, it's all immaterial as UK law doesn't apply (and I only took a short qualification in it so I know it's fiendishly complex anyway).
EDITED to remove information I had included in the original post
The new company has to offer employees a "transfer of previous employment" - so even though you're working for someone else, your history at the previous company is moved over with you. So if they wanted to get rid of you, they would then have to go through a redundancy process - which involves explaining why they're letting you go, offering you alternatives and giving you a payout based on your length of service.
And I'm completely lost with Debian releases.
Partly, you need mobile now, so any Rails stuff is likely to be back-end and hidden. Plus big investors like to go for the exciting stuff.
But if you're looking at companies aren't household names (taking smaller amounts of investment), there are lots out there.
Syft (recruitment) were founded in 2016 and have revenues of over $100m per year - although that's partly due to acquisition by a larger competitor, so when I just looked, separating their valuation from the group wasn't immediately obvious.
I've freelanced and contracted across a few niche industries (construction, print, airport signage management!) where I was building something against competitor software that I discovered was at least partially built with Rails. Those big players in each niche would have revenue in the tens of millions and from what I could see, very small technical teams.
But anyone outside those industries would never have heard of these companies.
There's some visual stuff: The default views, font choices and colours are really nicely put together (and I've tried tweaking VSCode to match but I can't get it to look as nice). For example, when viewing a git diff, it displays sweeping curves, which move and bend as you scroll, connecting the changes on both sides.
There's some Panic stuff: I like the integration with Transmit (which I use all the time). And I used to use the "publish" function all the time (develop on macOS and push to a Linux box to run tests etc).
And there's the fact that it's a native Mac app - I'm an old-school Mac user and there's a definite difference in "feel" between Mac apps and others. I'm not a purist about it (I have tons of Electron stuff installed), but when I use a Mac app I notice it. Plus I often get VSCode randomly slowing down to a crawl causing lots of annoying type-ahead, which doesn't happen with Nova - which I guess is a combination of Electron, JS and extensions combining.
But Panic has a reputation for sweating the details and it shows throughout the UI. Plus I feel good supporting a tiny company working in a niche market.
But functionality-wise it falls way short of VSCode - especially with extensions and dev-containers. The way VSCode + Remote Docker Containers feels like you're developing locally when actually everything is happening in a container on a Linux box somewhere halfway across the world is quite amazing.
As long as your code makes sure it takes account of that flag everywhere that it is used. Otherwise your new feature could "leak" into the system for everyone else.
Plus, as systems grow in complexity, there's always a danger that features step on each other. We'd like to think that everything we write is nicely isolated and separated from the rest of the system, but it never works that way - plus we're just a group of squishy humans who make mistakes. There will be times when having Features A and C switched on, with B switched off, produces some weird interactions that don't happen if A, B and C are switched on together.
""" Dear <<WHOEVER>>,
I'm writing to inform you of a change that Google is proposing which will:
1. Reduce the ability of the security agencies to do their jobs
2. Limit the ability of ordinary citizen to access the internet
3. Lock control to big tech companies and reduce innovation in the technology sector
As a citizen of <<COUNTRY>> living and voting in <<REPLACE>> and a software engineer with X years of experience, I believe this proposal (called Web Environment Integrity or WEI), although presented as improving security and privacy, is damaging because ... """
(edit: formatting and expanded the final line)
The OS, the development environment and the application (both code and live objects) where one and the same thing. To ship an "app" you would export the image and the user would load it into their Smalltalk VM.
They both achieve the same aims - reproducible setup - but (on Linux) a container is uses less resources than a VM, so it's lighter to run them both side by side. This matters for developer machine setup.
When it comes to production deployments, I haven't even started looking at k8s because I don't need that level of complexity.
Thank you very much.