mst

84 ms·

811.
by mst 4y ago
Wouldn't be surprised if that wasn't a "let's send all the random domains we have lying around to the main site" bulk change and whoever did it didn't realise and if anybody's reading the emails they have
812.
by mst 4y ago
Mmm ... while e.g. in React a lot of state libraries are specialised to React, I've had a fair amount of success using e.g. MobX for state management and React as the view rendering layer it was originally advertised at. But yes, it&#x
813.
by mst 4y ago
The usual heuristic I've encountered is that a library is something where your app code uses it and asks it to do things, and a framework is something where your app code hands off top level control and the framework asks your app code
814.
by mst 4y ago
That would rule out almost all server side templating systems, and most non-JSX client side ones (svelte, vue and angular all involve it to some extent) so I don't think that's quite right. I think maybe you've misread the au
815.
by mst 4y ago
I would still have gone with a higher length for the meta stuff, given the 2730 character limit on indexing I'd've thought 2048 would probably be fine and much less likely to result in a long path unexpectedly ventilating somebody
816.
by mst 4y ago
> That said, I think the operator you're looking for is the feed operator, ==> Yes, yes it was. Your clarifications, corrections and elaborations are much appreciated.
817.
by mst 4y ago
I learned lisp (well, mostly scheme) just enough to be dangerous - and to have a lot of fun. I don't end to find myself -writing- lisp very often but in a lot of cases I end up -thinking- in lisp and then translating across to whatever
818.
by mst 4y ago
It's notable that raku (previously known as perl6) lets you write things in either direction, if I remember correctly something like @source >>> map { ... } >>> grep { ... } >>> my @sink; though note I
819.
by mst 4y ago
Why the {1,255} ? Pg's text type is not varchar, it can get a lot longer than that and still index just fine, and while I can see a restriction on the pre_release stuff -maybe- being useful, compilation/build metadata doesn't
820.
by mst 4y ago
I think regarding it as a one-time payment for individual use with free upgrades within the current and next major version is a reasonable use of the term 'one-time payment' in that while you can't upgrade any further after t
821.
by mst 4y ago
> As a critique the fact that developer experience is on the roadmap rather than thought about from the beginning is a little off-putting Implementing it is on the roadmap but that's no evidence that it hasn't been thought abou
822.
by mst 4y ago
Ports is explicitly async and therefore only viable for a significantly limited subset of purposes. This has been discussed at length elsewhere in this thread, on elm related discussion boards, and in multiple articles. Ports is the -prefer
823.
by mst 4y ago
If memory serves, dev.to tends to be downranked or outright filtered by a bunch of places. (I have no idea how or why that came about, I've merely observed people having all sorts of trouble getting posts on there visible in aggregator
824.
by mst 4y ago
An N=1 example of an instance where a line of reasoning produced an accurate answers proves that it -can- produce the right answer, but does not, in fact, tell you anything beyond that about how likely it is to produce the right answer in a
825.
by mst 4y ago
> given the revolution in recent years in codes of conduct and DEI, I suspect my odds are better with newer communities, as there are now plenty of "antibodies" out there. A lot of that stuff can easily just enable a different
826.
by mst 4y ago
This is a poor line of reasoning - pretty much every community acquires an ass at some point and when it's not something they've dealt with previously it often takes them a while to figure out how to react. The question is how the
827.
by mst 4y ago
Opinionation is often useful but it's best implemented with an escape hatch of some sort for when you run into a sufficiently weird situation there's not actually a sensible way to deal with it. I don't particularly mind if a
828.
by mst 4y ago
I quite like the "stick a display next to the monument explaining the history and pulling no punches while doing so" approach, optionally (and in some cases I suspect highly preferably) having relocated the thing to a museum first
829.
by mst 4y ago
My British Indian friends tend to regard it as a subject more worthy of black humour than of bearing a grudge. "Sure, your ancestors were arseholes, but do you have any idea how much money we make off you just by being capable of selli
830.
by mst 4y ago
Pointing out the existence of the side effect of triggering/accelerating industrialisation is in no way apologism for all the awful things that were inflicted on the countries in question (being English, I've spent a fair amount o
831.
by mst 4y ago
I've heard anecdotes from nonwhite Intel employees who claimed that that was definitely happening there and it meant they could basically only bother to do any work when they felt like it because nobody expected decent productivity out
832.
by mst 4y ago
Vista had a lot of genuine security improvements for corporates, the extent to which you could create a much more reliable environment with judicious use of group policy was actually genuinely impressive. Honestly, apart from the horrible m
833.
by mst 4y ago
I keep seriously considering trying https://logtalk.org/ to get myself object orientation in prolog - haven't done so yet, expressing no opinion as to whether it's a good idea in practice, but it definitely looks
834.
by mst 4y ago
"Do X with AI" is obviously going to be something where competition should be expected. Cloning the UI and the launch tweet was still a bit much, though.
835.
by mst 4y ago
A service can run in a state of if not benevolent, then at least ambivalent, neglect for quite some time without it being a disaster for the users. I would suggest you start poking around at possible alternatives just in case, but not as ye
836.
by mst 4y ago
Given a Heroku employee showed up in a different subthread of this comment section saying thay wanted to change things but couldn't, in spite of a long discussion between the technical and legal sides trying to find a way to do so, it
837.
by mst 4y ago
My guess would be that a tiny percentage of accounts didn't get their notices sent, nobody complained about it because they didn't realise they were supposed to be getting them (or at least for whatever reason no such complaints w
838.
by mst 4y ago
> Why not just start charging for the postgres db, and only delete if there's no active billing? Probably because the original terms you agreed to were written not anticipating Salesforce perpetrating this and so while I would not a
839.
by mst 4y ago
At a guess, Salesforce bought it hoping it would take over the entire space rather than merely having the capacity to be one profitable provider among many, and lost interest once it became clear it was going to be the latter rather than th
840.
by mst 4y ago
When they were written, short sighted acquirers yeeting the free tier was likely not something the people writing the relevant clauses were even considering as a possibility, and honestly it's such a ridiculous decision from a commerci

More ›