There are some rough edges but this combo is quite refreshing after React. The best thing is that I could omit npm from my stack. Having just a monolith (Go) server greatly simplifies things if you're an indie dev.
TVs are much less of a “commodity” of course, but it’s a nice experiment that I’ll iterate on a bit more with time. Also, first deploy on Railway (was nice enough, definitely compared to Heroku, but they have a way to go), and using other libraries I wanted to learn.
Will probably start grouping models better soon, and offer other filters.
BTW: If you plan to do something like this with PAAPI (Product Advertising API), know that Amazon has the constant axe of banning you if you don’t generate “qualified” sales for 30 days straight.
[1] I didn't know about the 3-sales precondition either. I guess some people bought albums on Amazon on my other music-related app.
There's clearly precedent as I know Jeremies diskprices qualifies. Fingers crossed that Amazon play fair...
I thought those were iffy because they were run so hard? If not, I need to go shopping:)
That said, a lot of the GPUs used for crypto, don't apply to AI, unless you really want to be constrained. Just be super aware of what you're buying and what you plan to use it for.
eBay only allows 5000 API calls per day for most APIs useful to me which is very easy to hit: https://developer.ebay.com/develop/apis/api-call-limits
My infinite scrolling implementation probably didn't help either but I couldn't help myself, it was so easy to implement with HTMX.
> Error: Could not find aspects. Most likely because the server is under heavy load. Please contact support at magicsourceltduk@gmail.com and tell me where you saw the link to this website because I have honestly no idea where all this traffic is coming from. Many thanks!
Aren't there HTTP request headers that tip this off?
https://stackoverflow.com/questions/21922143/why-isnt-the-th...
Why this is good for anyone other than Google Analytics is beyond my current understanding.
Again nothing against the website itself, just unfortunate experience in practice.
Also, some items are listed but out of stock, which should be filtered out.
It doesn't look like you have EPYCs listed, or Threadripper? (These are some of the best CPU deals on eBay.)
To your other point, EPYC and Threadripper are listed now:
https://www.cpuscout.com/?Processor+Type=Epyc
https://www.cpuscout.com/?Processor+Model=AMD%2520Ryzen%2520...
Error: Could not retrieve items. Please contact support.
There are some rough edges around using `script` templates[2], for example it doesn't allow you to pass `this` and `arguments` from HTML event handlers[3]. This is not a show-stopper though, because you can always fall back to just defining your event handler in an HTML <script></script> block, albeit without type checking of the arguments and deduping the scripts. Also it hurts Locality of Behaviour which I'm a fan of.
That being said, I think it has some great potential. I can completely imagine people building fully-fledged UI libraries in this once component reusability is improved.
But the best part of using templ for me was that I could completely get rid of Node and NPM from my stack.
How was your experience?
[1]: https://templ.guide/syntax-and-usage/template-composition
[2]: https://templ.guide/syntax-and-usage/script-templates#script...
But being able to break things into reusable components with templ is compelling (and works fairly well from my experimenting). I’m just not in love with how you pass data into it and I ran into a few awkward points with the string interpolation of data when doing inline scripts.
I’m sure if I spent more time with it, I’d overcome these issues quick.
Tried disabling adblock, checked devtools which has no failed requests or errors though there were 4 "itemspecifics" requests that all returned 204 with no body
The Aus version went offline for a while so I built this quickly. The day I launched it came back online haha. Oh well, was a fun experience.
Initially was static html (generated by python) but that was leading to large page sizes, so I transitioned to ag-grid, which worked surprisingly well.
Got a 4xx or 5xx error on this (probably important?) URL. Told me to contact support.
CPUs go into motherboards which use power supplies and RAM and a storage device to boot and run operating systems/code
This all adds up once plugged in to "at the wall" power pull (basically measured in watts per hour * 24 hours = how many kilowatts a day)
Then, you take how efficient the hardware is at say, a proof-of-work mining algorithm (hashrate)
Then you can sort by which CPUs are most efficient
I've yet to find a database that does this (probably for good reason, mining is pretty dumb)
