That seems like a good bit of psychology as it accommodates both people with the mental fortitude to type in their genuine max bid in the first place, and also people who don't really know what they're willing to bid until they see somebody else bid higher.
Auction site design where most every transaction is a very material amount of money for buyer and seller probably have different trade-offs from something like eBay where most items are rounding errors compared to the income or wealth of the participants.
For example, think about "sniping" from the seller side. Sellers are rightly concerned about any wrinkle of the bidding process that might leave money on the table. Automatically extending the time so that every potential buyer has time to "answer" a new bid soothes the concern that buyers were willing to pay higher, but they didn't have the technological prowess to post their bid in the last 0.3 seconds.
Obviously anybody can post gross things by running an image generation/editing tool locally and publishing the results. People then mostly blame the poster whose name it then appears under.
Seems like a pointless and foolish product design error for X/grok to publish arbitrary image generation results under its own name. How could you expect that to go anything but poorly?
It's not just a matter of publishing it under its own name. It also massively reduced the friction to do so compared to needing to run the image through an external tool and upload the result. That friction would greatly reduce the number of people who do it.
In the US, it used to be that if you made credible threats against people you could/would be prosecuted. Social media made it so common in that no district attorney goes to the trouble of actually finding prosecuting people for doing this.
We can expect the same level of institutional breakdown with regards to various types of harassment, misappropriation, libel, and even manufactured revenge porn from AI.
It’s even worse as the requestor doesn’t vet and approve the image. That seems to have removed editorial control from the requestor. This bot could also mess with user who are not trying to do bad thing X, but the black box bot decides to throw in some offputting stuff and then also associate your name with it.
I keep coming to the same conclusion with X as they did in the 80’s masterpiece War Games.
These tools always fall short, not because the teams making them are bad, but because the underlying chat tools they build on are adversarial to the idea of a third-party UI replacing their UI. A new entrant might escape their ire for a while, of course.
Sure, you can have your LLM code with any JavaScript framework you want, as long as you don't mind it randomly dropping React code and React-isms in the middle of your app.
c appears to be the speed limit of the propagation of information in the universe - never say never, but so far it appears quite unlikely any new physics will overturn this.
I'm always thrilled to see eCharts mentioned anywhere. It is a highly featureful, complete solution for making sophisticated data-intense charts. Various commercial alternatives pale in comparison.
Likely so, but you have probably listed a bunch of organizations already utterly swamped with eager and qualified job candidates relative to their hiring numbers.
I totally believe they get swamped with eager candidates, but highly experienced ones?
Someone ex-NASA may well have deep experience in certain specific areas which few other candidates could claim.
The thing about a voluntary "deferred resignation program" – the people most likely to take it are those who are confident they can find good opportunities somewhere else. If you didn't have that confidence, you'd be much less likely to sign on to it.
NASA is still around. The layoff announcements for contractors at certain locations have been staggered as far as I know.
Still - it appears to be a tremendously hurdle for her to find alternate employment with her skillset in parts engineering without physically relocating - which would necessitate selling her house and her husband finding employment at the new region as well.
Shit happens, what can you do about it? Do you think garbage men, teachers or doctors will care about the tough job market of SW engineers? Everyone's job and everyone's lives have challenges, nobody else will cry for you, it's still up to you to deal with whatever problems life throws at you.
No. Flip it around. I care about the salaries and working condition of garbage men, teachers and doctors, even if they don't value mine. All three of those jobs you listed have vested interest groups who are standing in the way of a better life for those who provide these essential services, or are artificially controlling the market.
What we do about it is educate the public and form institutions that are motivated to protect these people. We failed on the former and now it's disrupting the latter.
Deciding whether I should care about another group based on whether they care about my own predicament is a straight path to evil.
> I care about the salaries and working condition of garbage men, teachers and doctors, even if they don't value mine. All three of those jobs you listed have vested interest groups who are standing in the way of a better life for those who provide these essential services, or are artificially controlling the market.
Do doctors really belong on that list? In my personal experience-I’m not a doctor, but lots of people in my family are, including my mother and brother (and when she finishes med school, my sister too)-I really don’t get the impression doctors are poorly paid at all. If we talk about those with established careers (so not junior doctors), the poorly paid ones are still earning twice what the average person does, and the better paid ones are off the charts. On average, medicine pays better than software engineering.
Oh, and I’m in Australia-in the US, medical salaries are even better than they are in Australia. Like take what people get paid in Australia and add 50%. Yes, American doctors would owe more in student loans-but when you are on US$400K, and the average US medical school debt is under US$300K, how long is it going to take you to pay it off?
What would handing money over to my government without any strings attached do?
In America we ostensibly participate in a representative democracy founded on the sentiment of no taxation without representation, and so our first duty is to be politically involved by educating ourselves holistically, voting appropriately for our local, state and federal representatives, participating in accompanying community building, wealth and knowledge dissemination in order to create and maintain the institutions which I mentioned in my previous comment.
Historically, the way to standardize how a component appears with Tailwind is to use component abstraction in whatever tool you are building with to accomplish that. Define a button once somewhere and then throw on whatever classes it needs.
If you were copy-pasting long strings of Tailwind classes all over, you were already doing it wrong before you even heard of Daisy.
Sure, you might make a `<Button>` UI component (assume React), but if it embeds 30 classes in it, when you server-render this, every button on your page is contributing ~30 classes worth of bytes to the payload sent across the wire.
The thing with Tailwind, however, is it reduces your options by picking a certain set of values, where with CSS you can choose whichever, so it becomes easier to have something that is more symmetric and looks better using Tailwind rather than CSS for this reason.
This can also be solved by having good design sense, and doesn’t necessitate a builder library. Having your own style also breaks websites out from all looking the same.
A challenge with TSX, and as I understand other similar tools, is that it doesn't support TypeScript decorator metadata. A few years ago, libraries using that started to get popular, so many older projects have a significant obstacle to moving away from running the TypeScript compiler JS output.
Starting a new project today, I think the right move is to use TSX or Bun or whatever. You want a roadblock at the very first moment you start trying one of these limited compatibility libraries, Because it won't work and then you'll pick a different library that doesn't rely on non-erasable TypeScript syntax.
The libraries that started to get popular using decorators years ago were using an --experimental compiler flag and should have known better than push that into production usages.
There's a Stage 3 decorators that now compiles in Typescript (>5.0) out of the box without an --experimental compiler flag, but it is subtly incompatible with that old experimental dialect and it will take some time before all those libraries catch up, if they catch up.
It won't run in Node (or this TSX) just yet because I believe Node waits for Stage 4 before enabling language features. (Deno has an experimental flag for it, as Deno supports Stage 3 features behind experimental flags.)
As far as I know the current bottleneck is Decorators are still only Stage 3, so the transpilers can transpile it as is (which I believe esbuild already does), but Node won't support running it until Stage 4.
reply