Hacker News new | past | comments | ask | show | jobs | submit | arunoda's comments login

Modular synths can be very expensive, but we figured out a way to keep the cost down while keeping the sound quality high.

We sell these modules, but we also release them with a MIT license & include the schematics, PCBs, code & even how & where to source parts.

We hope to bring modular for every musician & bring the cost less than buying software plugins.


Meteor community is the best OpenSource community I have ever worked with. Unfortunately, the framework couldn't reach it's goals & we had to move on into other things :(


There still isn't an APM for the Node ecosystem as good as what Kadira did so economically and easy to set up.

My startup interacted with everyone in the Meteor ecosystem. Positive selection because the technology was so good compared to everything else at the time. But recruiting was horrible, getting support from community investors was horrible, getting support from MDG was horrible.

The problem was, how did a Meteor consumer align with Matt and Geoff's goals? What were those goals, exactly? I'm sure people who worked at MDG felt the same way. They were too young to articulate it at the time. My company didn't align with their goals. Did anyone's?

It's a microcosm of Y Combinator's serious, persistent cultural flaws. The Meteor technology wasn't perilously flawed, that's a red herring. They know how to write useful web frameworks. But I didn't live in San Francisco - let alone Sri Lanka - and I had no desire to volunteer at the Burning Man airport or drink rare cases of beer or cavort with people who lose elections. Those were their most visible goals!

Like Jesus fucking Christ, a reply to an e-mail we sent to Matt or Geoff would be nice. We used and promoted your (Matt's) thing - we were first class evangelists with a fast growing product. But it seemed there was a missing cultural alignment. Too bad.

How did Kadira have better relationships with Meteor customers than MDG did? This guy whom I'm commenting on answered emails and made phone calls.

And maybe this is why React is big. Their goals were: find people to work at Facebook. Great, crystal clear. You knew what the deal was. Punchline to every conversation: "Oh, thanks for contributing to React, this is good, do you want to work here?" They didn't give a fuck if you met their overarching theory of affirmative action for libertarians or whatever. They just want good developers.

You could use their thing, and if you wanted to get to know them, that's what it was. Kubernetes? They (Google, Amazon, Microsoft) want you to pay for their cloud services. Clear as day. You contribute to it? Their deal is to copy it and sell it. They're not going to hire you. Fine.

These sound like business transactions. That's great. I didn't see a business relationship with MDG. They cared about other shit that didn't matter. It made developing for the platform as an evangelist suck.


Definitely agree here. It was a great community. I ended up hitting a point where Meteor just didn’t fit performance profile I was looking for and at the time fairly inflexible for which type of DB could be utilized.


> Just to clarify, this is what the author wanted to do. You can create distributed apps easily using Fleek or by manually uploading to IPFS, Arweave or Filecoin.

Seems like the author has never build an app before. There nothing easy even with the current tech. It's much harder with the tech they mentioned.

Even with that, there's a centralized system anywhere. Liek Arweave's DNS system etc.


You don't need the source code to make a executable version of the Game. And it won't take 1 hour on a decent machine.


It's not traditional LOD baking. There's no LOD baking. It's the new rasterization system doing the whole work.

And most of us doesn't use fast SSDs like in PS5 and it works really well. Also these engineers said, it even works just fine with slowers HDDs too. Because, they don't stream meshes for each camera movements. But it's a continuos setup.


Did you heard about something called Next.js


This is something I did with fast.ai - https://deeplearningmantra.com/


Yes. But all of the time we poll the CDN not the production app. So, it's not like traditional polling.

This is thanks to Next.js Static Regeneration features.

Basically stale-while-revalidate header support.

Ref: https://arunoda.me/blog/what-is-nextjs-issg


The is not only GKE. But for GCE as well. I cannot create instance is almost all zones. I tried both preemptible and normal as well.

Always saying resource not available. My account is a pretty new account.

In contrast, one of my friend is having a pretty old account which is very active. He has no such issue.

So I think due to this issue, Google has enabled some resource limitation for new accounts.

But they should properly communicate this issue.


You can alias your deployment and try to add a scaling rule to the alias.

So, you don't scale up and down as you deploy. Once you call the `now alias` it'll take care of the scaling.


Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: