byearthithatius

Regardless of if this is common its getting popular because its objectively hilarious and we can all see it being possible.

Love it when someone who makes complex, helpful software is rewarded for their efforts. More stories like this!

So what are the other things? You said he glossed over them and didn't mention a single one.

This is wildly and seemingly unnecessarily chaotic and I am at a loss for its purpose. Probably just my own ignorance/laziness. But it does feel like its _trying_ to be hard to understand/navigate and overly random/weird. My curiosity got the best of me but I left feeling I just wasted 10 minutes.

EDIT: website is just an inside joke and not helpful. OS is real but also not helpful. https://www.reddit.com/r/plan9/comments/1mr6cyr/comment/n8xp...

Its not working for me, there is an SSL error. `SSL_ERROR_RX_RECORD_TOO_LONG`

Love the top level domain haha! Incredible.

its not good and just a portfolio but I love HN for years now so I want to put mine on this thread for posterity: elginbeloy.com (https://elginbeloy.com)

Thank you for this!

kinda like that hacker news hacked it pretty quick haha

Is there a place I can read about taking unique creative approaches to original topics/games/concepts like this? "Thinking Different with Basics". I like this so much but its because it gets at an essence of creativity applied to the obvious I don't know how to learn or search for:(

Anybody who has meaningfully engaged with short-form dynamically adapted video content and read a book can EASILY tell the difference. It is Morphine vs Fentanyl

Do you think its true both then and now, or rather that people are always seeing the past grass as more green?

You say in your comment: "Anybody with a computer science education ... should be able to tackle this one" which is directly opposed to what they advertise: "You don't need a computer science background to participate"

So incredibly niche and specific but also theoretically viewable/verifiable. This is incredible.

"CNNs and Transformers are both really simple and intuitive" and labeling a bunch of images you downloaded is not simple and intuitive? It was a team effort and I would hardly call a single dataset what drove modern ML. Most of currently deployed modern ML wasn't trained on that dataset and didn't come from models trained on it.

100% agree but not just military. Self-driving vehicles will become the norm, robots to mow the lawn, clean the house, eventually humanoids that can interact like LLMs and be functional robots that help out around the house.

Curating a dataset is vastly different than introducing a new architectural approach. ImageNet is a database. Its not like inventing the convolutions for CNNs or the LSTM or a Transformer.

This is super cool and I want to read up more on this as I think you are right insofar as it is the basis for reasoning. However it does seem more complex than just that. So how do we go from coordinate system transformations to abstract reasoning with symbolic representations?

Poorly designed studies, materials proposed without insight into ramifications and manufacturing, and P-Hacking has ruined the publics trust in science. I blatantly just ignore any headline like this now. Can't trust science anymore.... sad. How many new "cancer cures" have been posted to Reddit and HN over the last decade that never came to fruition.

Not to say doing the science and studying to find new approaches is not beneficial. I just think we need to reconsider how we communicate new research. Its like how CEOs hype up AI products at this point. "This will change everything ..... potentially maybe in twenty years (omitted)"

I hear so many counter-logical ideas proposed with "scientific evidence". Poorly designed studies and P-Hacking has ruined the publics trust in science. I highly doubt flossing is a net negative for almost anyone.

Its all either a pre-prompt/context edit or coding integrations for "tool use". Never anything _actually new_

There are a million tools which literally just add a pre-prompt or alter context in some way. I hate it. I had CLI editable context years ago.

Think about how fast progress is being made now. When I was a kid in the early 2000s we would see some basic robot progress on movements (almost always from Boston Dynamics or sometimes China) and we thought it was incredible. Robot dogs running was amazing and five or so years later a backflip blew our minds. Those robots were specially designed and didn't look humanoid. Now we have bi-pedal humanoid robots and they walk and move fairly capably - even able to get up after falls. Now within the last year I have seen them learn Kung Fu, become really fast at getting up, become resistant to being knocked down by quite a lot of force, and now even doing tasks like those shown here.

Just imagine 2050 if the progress continues at this rate. I am both excited and really scared.

I am probably just misguided but multiple things you say you "wouldn't call a reactivity engine" only exist to support updating DOM (reactivity) efficiently. So what would you call them? They only exist to update the DOM, which is itself the reactivity we all want. Technically you could just getElementById and update it, but react has what I call a whole "reactivity engine" to do it for you.

Agree, that is why I am confused by his question to me. Like SSR should be the default. Why does your server by default "hydrate" the client bundle. Why can't the client bundle request data as it needs it (then we can only request what the user needs). Skeleton UI it while you fetch. Then you have great page load time because you just return a static HTML+JS bundle that was non-conditionally built. In SSR it talks to the DB before it even constructs the bundle, that is oof right? So you are faster because you don't even gen the HTML until you talked to the DB? I give the user plain HTML instantly and talk to the DB while I give them a UI indicating its loading. SSR just moved the load time to before initial render. Stupid IMO.

Why is it the default for you? You are worrying about hydration complexity and all that when you introduce it, so it better have some benefits.

My default is a small page that client then fetches any additional data it needs. If its long load time skeleton UI it. I also have not seen the SEO benefits at all.

So again _why would I_ unless I needed to do stuff on the server to make the client bundle, which I don't.

A lot of these YC companies doing this could literally just be using a fetch because their backend is dead simple REST.

I mean the docs of most of the frameworks are written in that framework even though its just static pages. Didn't even need the framework but not using your own framework for docs feels ... bad I guess?

I have over ten years experience and the distinction isn't always clear to me.

Example: This logistics SPA I was building I realized could just be single pages with some data for most of the stuff (tracking, inventory, etc...) but for admins they wanted a whole dashboard. This was a conditional on some value of the stored session user. So it ended up being kinda a website for parts of it and an SPA admin panel if the user conditionally matched some privileges. Probably should have been separate stacks but they used the same data so early on they made it the same Next app.

I don't think the whole website vs app thing is always as simple as static blog pages vs full fledged JS-heavy app. There is a spectrum and overlap even within a single "application" because of various requirements.

Your last sentence is the most accurate. I don't think its primarily ignorance, its just trying to meet all the requirements while retaining some level of organization in the codebase.

This is probably the best answer to my confusion. Not too negative or overly optimistic. We are just still fleshing out how we want to do this and there are a lot of cooks in the kitchen finding various ways to make the same dish.

Main React has been pretty stable for a few years but the ecosystem to serve React bundles has not been.