Hacker Newsnew | past | comments | ask | show | jobs | submit | mcintyre1994's commentslogin

Very cool, I like the variety of demos! On the candle sticks streaming demo (https://chartgpu.github.io/ChartGPU/examples/candlestick-str...), the 1s/5m/15m etc buttons don't seem to do anything

Good catch! Thanks for actually clicking around and finding this - added to my issue tracker.

Can't tell what this demo is streaming, looks like a static line but it's working hard on something. It can't seem to decide whether to display the top number in red or green either.

The article says browser support is limited, but good docs: https://developer.mozilla.org/en-US/docs/Learn_web_developme...

Out of interest what's an example of styling that the radix/shadcn version enables that their approach doesn't? I was able to (AFAICT) replicate the radix docs example by just moving their styles around: https://codepen.io/mcintyre94/pen/pvbPVrP

In the example they are just using an empty <RadioGroup.Indicator/> for the pip as it is easy to target with a classname, but you can put any content in there instead for e.g. card-style radios (as used for complex selections, like a subscription tier).

By using radix, the underlying behaviour is compliant and identical for each of those implementations - you just change the content. Radix isn't looking at it like an html radio element, it is looking at it as a completely unstyled unique item selector.

The pseudo-element styling approach limits you to 3 layers - the container, and the 2 pseudo elements, none of which you can provide with meaningful content besides plain text. The best you can do is provide a basic styles and set background image. For anything else you need to use labels to either wrap the radio (in which case you can access state via sibling selectors) and/or ref them with "for" (in which case you cant access the state).


I think this is the equivalent of the radix demo (which has better styling than the shadcn one) in plain html/css: https://codepen.io/mcintyre94/pen/pvbPVrP

Copied styles from the radix docs: https://www.radix-ui.com/primitives/docs/components/radio-gr...


Fun exercise! https://codepen.io/mcintyre94/pen/pvbPVrP

Everything in styles.css in that example maps to the vanilla input, so you just have to move them around a bit. Should work at least as well as theirs across browsers, because it's vanilla inputs and the same CSS.


The case is made. That's awesome.

I don’t really understand the argument for prediction markets if you don’t have inside information. The reason they beat other forms of news is because insiders are incentivised to bet, that makes some sense. But surely an investor without insider knowledge will always make less money on a market where they’re trading against insiders than one where they’re not.

You forget that people are not necessarily doing this for rational reasons.

Some people do it for for entertainment, some people are gambling addicts, some people think they have a strong grasp or inside knowledge when they don't.

It is, at root, a casino. Apply your lens to any casino game, and it shouldn't exist (some very narrow exceptions apply in the casino).


It is not a casino in the sense that in the casino you are better against the house. Polymarket is basically an arbiter with financial infrastructure.

Not all casino games are played against the house. The best analogy would be a game like poker, where the house takes a small percent of every pot (the rake). Other than that, money changes hands between players. The game has an element of randomness and luck but there is also a large element of skill. Players have a wide range motivations and skill levels, from casual players and thrill-seekers to professional players.

I don’t know how this works but assuredly polymarket takes a cut, right? So if we were betting on a coin toss on polymarket, the payout would be less than 2 for both heads ands tail after accounting for polymarket’s fee. That’s not different from the rake for a poker game in a casino?

For the purposes of understanding the behavior of those laying down bets, it is an irrelevant distinction.

> I don’t really understand the argument for prediction markets if you don’t have inside information.

If you don't have inside information and you participate in prediction markets, you're there mostly to provide liquidity.


The argument is not that you should bet on prediction markets, the argument is that you should use the odds from the market to make decisions about the future.

But they don’t work without someone making the argument that some non-insiders should bet on them right? Because the insiders aren’t going to bother moving the market for us if there’s nobody to take money off.

The traditional way to square that circle is to say that someone who's interested in the answer should subsidize the market. Essentially they provide liquidity to the market which essentially pays people with accurate information to bet. Some work has been done to figure our effective ways of doing that. In practice, it seems like gamblers often provide enough liquidity that this is not needed

If you don't have insider info, they are betting houses. Prediction Markets is just a cynical euphemism.

I suspect that in practice, because a lot of online gamblers spend a lot of time specifically on X, they’re more susceptible than average to fake news.

Source for this stat?

> Your outlook above is too self critical. This is the first time an AI has beaten this park much less played a full game of RollerCoaster Tycoon through a TUI. There are important learnings for B2B SaaS. This isn't LinkedIn (it is, in fact, LinkedIn). But seriously. What can we learn here.

From the transcript: https://htmlpreview.github.io/?https://gist.githubuserconten... :)


The features it asked for in this case were better tools, I thought they were really sensible. It said it wanted a —dry-run (like the CLIs the rct one was modelled on), it wanted to be able to segment guest feedback, and it wanted better feedback from its path tools. Those might not be actually possible in rct, but in a different context they’re pretty smart requests and not just verbose edge cases.

I’d be curious what proportion of their usage is on the mobile app and doesn’t need to worry about a significant number of users having adblockers. My instinct would be probably a decent majority is mobile, but not as high as something like Facebook, but that’s just a guess.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: