Readit News logoReadit News
kylecordes commented on eBay explicitly bans AI "buy for me" agents in user agreement update   valueaddedresource.net/eb... · Posted by u/bdcravens
BeetleB · 20 days ago
> They have a built in "sniping bot" - by allowing you to type your highest price, and it will auto-bid for you until that price.

With ubid, you also had the feature of letting it bid to your highest price. Yet they still extended the auction if someone outbid your highest price.

kylecordes · 19 days ago
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.
kylecordes commented on eBay explicitly bans AI "buy for me" agents in user agreement update   valueaddedresource.net/eb... · Posted by u/bdcravens
giobox · 20 days ago
This is how the popular car auction site bringatrailer.com bidding process works for cars sold on their site too, a quirk of which is that it makes watching the end of the auctions live online kinda fun, especially given the discussions that break out in comment section on each car up for sale while folks nervously watch the current candidate for the final bid cool down.

Much like your example, in the two minutes before the end of the auction, every new bid placed extends the auction clock by another two minutes, the winner hasn't won the auction until two minutes have passed with no further counter bids.

> https://bringatrailer.com/how-bat-works/

kylecordes · 19 days ago
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.

kylecordes commented on X Didn't Fix Grok's 'Undressing' Problem. It Just Makes People Pay for It   wired.com/story/x-didnt-f... · Posted by u/pavel_lishin
kylecordes · a month ago
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?

kylecordes commented on Show HN: Amber – better Beeper, a modern all-in-one messenger   useamber.app/... · Posted by u/DmitryDolgopolo
kylecordes · 5 months ago
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.
kylecordes commented on Cursor CLI   cursor.com/cli... · Posted by u/gonzalovargas
wilg · 6 months ago
Think how many JavaScript frameworks can be vibe coded now!
kylecordes · 6 months ago
(This is an exaggeration:)

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.

kylecordes commented on Project Hyperion: Interstellar ship design competition   projecthyperion.org... · Posted by u/codeulike
virgildotcodes · 6 months ago
Reading through this in detail just cements that we are never leaving this solar system unless we discover some new physics to get around our speed limitations.
kylecordes · 6 months ago
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.
kylecordes commented on Apache ECharts 6   echarts.apache.org/handbo... · Posted by u/makepanic
kylecordes · 6 months ago
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.
kylecordes commented on 4k NASA employees opt to leave agency through deferred resignation program   kcrw.com/news/shows/npr/n... · Posted by u/ProAm
orochimaaru · 6 months ago
Why won’t the skillset be transferable to places like space x, Amazon kuiper, blue origin, or any of the big defense tech or start ups (eg anduril)?
kylecordes · 6 months ago
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.
kylecordes commented on DaisyUI: Tailwind CSS Components   daisyui.com/... · Posted by u/a_bored_husky
qq99 · 7 months ago
I'm surprised that a lot of the comments seem to be missing the reason that this project exists.

In many tailwind projects, you inevitably end up wanting to standardize how a button looks, how a field looks, etc., rather than copy+paste the same 20+ tailwind classes that you need to implement a nice looking button in tailwind.

Can you just apply it to `button { @apply flex items-center blahblahblah; }` in app.css? Of course you can. Or you can use the btn from DaisyUI.

I think DaisyUI is just a shortcut for many common UI components that you will inevitably want to build out and that you will necessarily eventually standardize in any app that grows large enough.

How does it differ from bootstrap? Well, you can continue to use tailwind for everything else that DaisyUI has not implemented. It's just an additive layer to tailwind. The project is at its core just a shortcut for common UI components.

As a user, my criticism is that many of the DaisyUI components seem to be lacking good contrast, so some just don't seem to be usable. The theming situation is really interesting and quite cool to use, but if you look at the example page, it just feels hard to read. I can't really find a light and dark default theme that look good to me (re: contrast and brightness). I think the color hooks might just not be there but I didn't dig far enough in.

For me, I've found a lot of value in being able to easily copy+paste parts of DaisyUI source code, e.g., a particular widget and modifying it to fit my design system, rather than use it in its entirety.

kylecordes · 7 months ago
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.

kylecordes commented on Run TypeScript code without worrying about configuration   tsx.is/... · Posted by u/nailer
kylecordes · 7 months ago
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.

u/kylecordes

KarmaCake day1601May 28, 2009
About
Software entrepreneur, developer, investor: 3 ventures in/out so far. LP to people smarter than me. Looking for the next thing now.

https://kylecordes.com

kyle at kylecordes dot com

View Original