It's weird to see the party claiming to be for free markets essentially go all-in on central planning. Black is white and up is down, I s'pose.
4,711 karma · joined May 2, 2014
As a web developer that's an immediate deal breaker. I use Sublime today and being able to run multiple LSP servers per file is a huge boon, it turns a very capable text editor into a total powerhouse. The way it's set up in Sublime with configuration options that can be applied very broadly or very specifically, while having defaults that just works is also just incredible.
While I'm super pleased with Sublime and a happy paying customer since at least a decade, and at this rate may well be for another decase, I'm always keeping my ear to the ground for other editors if nothing else just to stay current. Zed's been looking pretty cool, but things like this will keep me from even just trying it. There's years of muscle memory and momentum built up in my editor choice, I'm not switching on whim.
Thank you very much for sharing this nugget of gold!
Seriously though, couldn't agree more. Criminally underrated indeed!
const durations = [
Temporal.Duration.from({ hours: 1 }),
Temporal.Duration.from({ hours: 2 }),
Temporal.Duration.from({ hours: 1, minutes: 30 }),
Temporal.Duration.from({ hours: 1, minutes: 45 }),
];
durations.sort(Temporal.Duration.compare);
console.log(durations.map((d) => d.toString()));
// [ 'PT1H', 'PT1H30M', 'PT1H45M', 'PT2H' ]Can't guarantee no issues, but my gut feel is you'll have a much better experience with 20 -> 24 for example.
I have liked it very much for the past decade or so, and at this rate, I'll most likely keep liking Sublime Text for many years to come. It's an incredible tool that does its job extremely well.
Worth every penny!
I would rate their driving as quite good, but their signaling of intent was terrible. More than once did I see them use turn signals, only to never actually turn. Turn the signals on, then off again, then on again, eventually turn perhaps but not always.
Humans are terrible at this too, but we also use more subtle and inadvertent signals like the slight movement to the line telling me they're likely about to switch lanes, only to see the signal go on halfway into it. Those subtle signals are easier to pick up on than a robot driving more or less perfectly straight while signaling, turning of signals, turning them back on again, and so on. Also super creepy with empty driver seats, and no one responsible to make eye contact with.
But the actual driving wasn't bad, as it turns out. Never had or saw a near miss, anything reckless or otherwise remarkable. I can see myself getting used to this tech and I would love for it to succeed, because man driving for anything but fun really sucks.
I'm in total agreement with you but I guess the AuthN/AuthZ train left the station ages ago and no one outside of the business of selling these tools actually care. Oh well.. :o)
I gave the question a +1 because I, as previously stated, read it to be genuine curiosity. Maybe a smiley would’ve helped, I don’t know. ¯\_(ツ)_/¯
My experience is that fixed price only works for very short (days and weeks, not months) projects that can be scoped very strictly. Even then, there’s a lot of risk of miscommunication and uncomfortable discussions. My rule of thumb is that if I’m doing a fixed price contract, it can’t be longer than two weeks. This usually amounts to very targeted fixes, upgrades, research projects. Things that are typically not so hard to time box.
Poor word choice aside, the advice really is solid. I’ve been a consultant for nearly 20 years, the last 10 as an independent, and it took many years of screwing this up before coming to mostly the same conclusions.
It's also backed – nay, pushed – by one of the largest and most successful tech companies in the world. A company that also made a point of releasing a very capable IDE to go along with it. Surely this has had some impact on its meteoric rise? :o)
(Wait – aren't meteors falling?)
You don't know me and I don't know you, but I know of you through your work on Tamagui. Very excited to see this coming from someone with your kind of experience – we desperately need something to challenge Expo and hopefully truly bridge the native/web divide in a way that actually works, without leaky abstractions everywhere.
Very hopeful that your experience and knowledge in the space will get us there – thank you for your efforts! I will be checking this out in earnest as soon as possible. Very exciting!
During development this would sometimes break but only in very specific circumstances, and because they were so absurd and seemingly specific to our local development environment I just added an error message saying "watch and amaze while the application eats itself!" Or something to that effect. It was inspired by an error I saw with the Discworld game for the original PlayStation.
Of course, once this hit production it turns out the det of circumstances necessary to trigger this error wasn't quite as specific as I'd thought, and support was overloaded by hundreds of people calling in to report the error, worried that their money was gone. Of course, people using these feature were high rollers placing very large bets, so management was not happy...
Fortunately I wasn't fired and we fixed the issue very quickly, but man I felt the edge of that sword really close to my neck. It was at one of my first jobs as well nearby 20 years ago. I definitely learned some valuable lessons that week. :o)
Turns out he was also using Comic Code, and he basically had the same feelings as you towards it. I thought what the heck why not, and gave it a go. Now I'm hooked as well, for the very same reasons.
Coding, somehow, is just more fun and enjoyable now. Moreover, it's probably one of the more legible fonts I've ever used. Didn't expect that!
I guess it's good business from the ad income sharing, and at the very least it's slightly more interesting than people posting reactions to reaction videos.
I was very vocal against the fundraising to purchase and free the blender source code back in the day, and had very harsh criticism for Ton, saying things like Ton ran NaN into the ground, why should we trust him to deliver on freeing Blender etc. etc. It was a divisive time, and people in the community said stuff like if you don’t like it, leave – and I did. I remember one guy saying “don’t let the door hit you on the way out.” :o)
I was very wrong in doubting Ton and the community, and I’m very happy to admit it. Blender is an amazing piece of software, and it’s wholly and completely free. It never would’ve been without Ton.
So Ton if your read this – thank you so very much for proving me (and many others) very wrong!
If you want to get real anal about it the API should probably called URI instead of URL. The latter should describe where to access the resource, not just how to identify it, and to truly be able to do that you must also know something about the scheme.
At the very least you must know whether the scheme imposes further restrictions on the individual parts of the URI, otherwise you can only determine whether it's a valid URI but not truly say whether it's a valid URL.
In practice no one really cares much about the distinction between identifiers and locators, and arguably it was a mistake to try and make that distinction in the spec. But it is in there after all and I find it a bit ironic that the authors of the JS spec chose to ignore it. There's probably good reason for it, but still.
Ps. I'm real fun at parties!