langcss

I'll send you an email.

It does thanks. Sounds like "support plus access to future versions when released"

A pricing table might help here.

A point of confusion is where it says both:

》Want unlimited launches of the latest launchpads? Need ongoing support? Reach out to (email)

》Reuse your code as many times as you like.

Is the first one a cloud offering and second referring to self hosted?

You need a lot more power. I found gpt4o struggles doing basic OCR of printed text by hallucinating alot, while tesseract engine (old skool) gets it perfect. You need the model to be powerful enough to do everything.

You can work around this by the way by sending the output through a checking stage.

So picture -> gpt4o -> out1, picture -> tesseract -> out2, out1,out2 -> llm.

Might work for sound too.

The built in DB makes this very interesting to me. Although I would prefer sqlite. The low LOC count is nice to know.

Minimilism is something that is hard to get right on the web. The cliche is people avoid django because it is too complex then hand build all its features anyway over time!

However some jobs are minimal esp. internal dashboards so there is a place for it. You may find fasthtml which is also minimal interesting.

Curious: why Java and not Go? Go seems more in line with being minimal. Especially for deployment.

And that day, I was told I passed the Amazon interview and was offered a job as a L4 Software Engineer.

I believe LLMs decimating the role of a software engineer requires AGI, which the second that happens decimates all jobs.

What it may do is change the job requrements. Web/JS has decimated (reduced by 90% or more) MFC C++ jobs after all.

The programmer doesnt just write Python. That is the how... not the what.

For clarity: do you want to be a software engineer, platform engineer, data scientist, ML expert or something else?

I asked it to prove Fermats Last Theorem and it started writing (some nonsense) into the margin. Which was funnny.

Cool project tho

If you can design a new encoding scheme, zero bits is enough.

Wow. Bike shedding really is expensive.

Related-ish: https://en.wikipedia.org/wiki/Nosebleed_section

> Most startups fail because they focus on scaling too soon.

You sure about that?

Other than that....Great site by the way :)

Next is odd because it gives lots of "high preformance" vibes with static rendering and image optimization. It is fast enough but not as fast as tuning up a classic MVC app which caching, avoiding JS bundles and React or deferring scripts etc. Send out the right cache headers and chuck a CDN in front.

Next is ironically fast if you prerender/static generate AND the client disables JS!

There is client state. The URL plus the sum of whatever partial swaps you did since loading the page.

Or worlds smallest cloud provider?

Im guessing paternal grandfather.

Thats odd because I remember people saying "when will Google start ads". Although probably thinking of the Yahoo style slow loading mess.

Trains... but they end up at your house.

A circle circumference is a line, is 1D?

An open source repo of selenium scripts for different banks would be a decent thing.

Yes because it is a question for a quant.

Reminds me of the "Nosedive" episode of Black Mirror.

Or better web standards allow everything you need for the common things in a web app to be plain html and css so that porting to JSX etc. is mechanical.

For example menu systems, popups etc. Yes there are html css hacks but they are indeed hacks. A checkbox is not a button or a parent menu.

A bit like "is this hotdog overpriced" amd trying to binary search the exact cent where it became overpriced.

Just check what cloud costs you may endure. Serving static CDN files is cheap. Dynamic image resizing costs. I use the simple img tag as I am not interested in that optimization.

A rare Show HN game that works perfectly on mobile, like an app. Good game too. Well done.

I see! It is a landing page "Inception"

Best to use SSO for SaaS passwords. This is where your whole team has a Microsoft or Google (or other identity provider) login administered centrally by the company that is further used to authenticate to various services.

As opposed to "login with Facebook etc." logins that are individually administered by each end user for each app.

This is low fruit for many things but often companies require you to be on an expensive SaaS pricing tier to use SSO on their product.

Next problem to solve is Software Engineer's cloud secrets. Use key vaults in your cloud for this. Use SSO to authenticate your team to that cloud.

Enable 2fa as much as possible. TOTP not SMS.

Finally you will need people to save passwords for some stuff. Lastpass or Bitwarden etc.

Avoid shared passwords. Sometimes unavoidable in which case rotate them often and when people leave too.

Check your pricing page amounts are weird (e.g. strike through $10 now $420), and and links are broken.