111–120 of 243 posts
Netlify CEO here. I spotted Little Workshop when I saw https://equinox.space/ on Hacker News and noticed it was running on Netlify. Loved the fluidness, speed and art direction of a game running directly in the browser and working smoothly on my phone. Immediately thought of them when we started thinking about a 5 million developer celebration and reached out. Love the result :)
Interesting. This consistently crashes my chrome browser whenever I get to the first glowing white checkpoint. But it's not like any crash I've seen before, the page reverts to a google search result I was on this morning. And the whole page is flickering white. That tab was closed long ago, but it seems something in this gets back to that state in memory, maybe a buffer overflow somewhere or something? While on the…
Nice! My favorite challenge was avoiding the glowing white dots along the path.
Right now learning about the company feels like a penalty which I doubt was the intent.
Also for anyone who hits a dot and is confused how to get out of the information screen - you just press the arrows. I tried escape and clicking for longer than I would care to admit before I realized this.
Super cool idea though.
Great job optimizing too. Runs totally smooth on my 2012 macbook and its decrepit HD 4000 iGPU, which is no small feat for web-games these days.
I'm one of the developers who worked on this project. Happy to answer any questions. More info on the project here: https://www.littleworkshop.fr/projects/5milliondevs/
This was really fun. Right before this little hole on the second level, my macbook started running a bit slow and the collision detection somehow sucked the marble into the floor. https://imgur.com/ZANb1cT
Earlier quoted context omitted.
Thanks. The WebGL rendering is based on Three.js. We're using Rapier for the physics simulation, and Howler for the audio. Our game engine is responsible for all the controls and updating things like the camera position (which follows the position of the ball at every frame).
Why did you choose to do things this way instead of using Unity WebGL? It's okay if the reason is, "because we make websites and the programming we know is Javascript" or whatever. It doesn't have to be about some objective comparison, like optimization or whatever, which isn't going to be true or necessarily matter anyway.
However, mobile browsers will be supported with Unity 6 web exports, still experimental currently AFAIK, but that should become a viable option soon.
This is fantastic!. Time to start speed running!
4 minutes and 21 seconds after few more attempts.
3 minutes and 59 seconds. Sub 4 is good enough for me :)
I think this is the first time I've ever seen an online game correctly tell me to use WARS keys for movement. Big props for handling non-qwerty layouts. Great job optimizing too. Runs totally smooth on my 2012 macbook and its decrepit HD 4000 iGPU, which is no small feat for web-games these days.
If anyone's wondering, the getLayoutMap method from the Keyboard API is what we're using to handle international keyboard layouts.
https://developer.mozilla.org/en-US/docs/Web/API/Keyboard/ge...
Earlier quoted context omitted.
Why did you choose to do things this way instead of using Unity WebGL? It's okay if the reason is, "because we make websites and the programming we know is Javascript" or whatever. It doesn't have to be about some objective comparison, like optimization or whatever, which isn't going to be true or necessarily matter anyway.
Unity WebGL is not supported on mobile and we needed the experience to be playable on both desktop and mobile browsers. However, mobile browsers will be supported with Unity 6 web exports, still experimental currently AFAIK, but that should become a viable option soon.
Hmm... Unity WebGL has worked correctly on Mobile Safari since 2013. Support has probably been flawless since around 2019. It has been supported in all the ways that matter for a long time.
Any chance this could get open-sourced? This seems like a great example of a lot of stuff for which there are few tutorials currently.
> This seems like a great example of a lot of stuff for which there are few tutorials currently. Not OP but, what exactly you feel like is missing tutorials? It's a nice little polished experience, but I don't think there is anything particularly innovative or difficult to build with the resources that exists today. Or is there something in particular that looks/seems difficult from what they shared?
Companies like Figma have shown that there is a huge appetite for solutions built on top of Canvas or WebGL, but if you don't have the privilege of working for one of these companies that built up lots of proprietary building blocks from scratch, it's much more difficult to get started.