HatchedLake721

If not, how do you know it was wrong for them?

FYI Uber migrated from Postgres to MySQL https://news.ycombinator.com/item?id=26283348

Here's to no one trying to patent it now!

It felt so weird after being spoiled by WeWork and left a very negative impression about Regus/Spaces.

See below from Euro NCAP and sort by "Vulnerable Road Users" (green person walking icon)

https://www.euroncap.com/en/ratings-rewards/latest-safety-ra...

All your products are extremely technical and target the worst market for first time founders - developers.

Developers, one of the most highly paid people in the world but also people who rather waste 4 weekends tinkering with something than pay you $5.

You need to solve business problems and I suggest build solutions for _non-technical_ people.

Find a business problem that's worth at least $99 p/m and niche down on it. E.g. do some research, speak with people, find manual/spreadsheet/data entry process in the business and automate it where possible.

It's better to have 100 customers paying you $99 p/m to make $10k MRR, rather than 2,000 customers paying you $5 p/m.

And it's not hard to sell $99 p/m product when you speak with business people and solve their problems.

You're also very technical, so I assume you have no sales skills or experience. You either need to find a business co-founder who'll do that, or be ready to reinvent yourself.

Also youtube around for Dan Martell, he's got a lot of great content from a few years ago around MVPs and early stage startups.

Shvetsiya vs Shveytsariya

Because React is a view library, not a framework.

Yes, web components might outlive React.

But no, they will not outlive my JavaScript framework, because web components don't replace routing, data layer, testing, authz, server-side rendering, rehydration and whatever else frameworks like Angular/Ember/Next.js/etc do these days.

Rendering a view is a small part of what front-end frameworks do.

Yes, if memory serves me right, yarn might've been first with `yarn.lock` before `package-lock.json` was a thing.

But why would I use yarn today?

I don't care about speed of npm install locally, I do it once in a blue moon.

I don't care if my pipeline takes 3 minutes (yarn) to install dependencies instead of 5 minutes (npm).

But 99.9% don't care about running non WebKit browser, so it doesn't cripple 100% of users because they are not affected by this.

Same as having no Flash support today doesn't cripple 100% of iPhone users, because they don't care about it.

Go and ask your friends/parents/family/grandparents if they're crippled by not being able to run a non WebKit browser and listen to their answers.

I'm not making up numbers, I'm generalising it.

There's 1.5 billion iPhone users in the world, and there's ~26 million developers in world, that's less than 2% of 1.5 billion. Only a set of ~26 million developers have iPhones, even smaller set know the word WebKit, and even smaller set of those that know what WebKit means even care that their iPhone cannot run a non WebKit browser.

So yes, I can generalise and say that 0.01% of iPhone users care about non WebKit browsers. I can make it 0.1%, 1% or even 2%, it doesn't change the point - a minority of techies who like to tinker with their gadgets (including some business owners who want to increase their revenue) want to force their needs on 99% of people by exposing over a billion people to new security and privacy threats and attack vectors.

All while for the last 15 years they were happily piggy backing in the walled garden that was designed this way since day 1 and playing key role in Apple's success building a marketplace of 1.5 billion people that was unimaginable in 2008. And then suddenly 15/30% became too much, please change the terms we were playing along for 15 years, open up the iPhone!!

99.99% of users don’t care.

That’s why iPhone today is still the #1 mobile phone with highest loyalty and consumer satisfaction scores for over a decade.

You don’t become an industry changing leader and stay #1 by “crippling 100% of users”. It’s just what you think is crippling, others don’t care about.

Microsoft in their last few years tried very hard to incentivise developers to build apps for Windows Phone.

But many didn’t bother. Some even only targeted iOS because of the reach and how amazing the development experience was, including less devices to test and support compared to Android and Windows Phone.

And this made the choice for consumers easier, when (I don’t remember the names) some very popular and big apps at the time were not natively available on Windows Phone at all.

Even Tim Sweeney never brought Unreal Engine to Windows Phone despite their promises and I’d say played part to build the current status quo.

Developers voted with their time to build apps for a 30% fee marketplace that suddenly was a gateway to distribute their work to millions of users worldwide that was not heard of before in the era of Windows Mobile. (pre iPhone)

And now they cry wolf about the system they’ve voluntarily helped to build.

My mom has an iPhone and I can sleep safe knowing she won’t install some dodgy browser or anything like that.

I’m happy such category of devices exist and I’m happy to pay a premium.

90% off year 1

50% off year 2

25% off ongoing

HubSpot charges ~$1,200 p/m for their professional Marketing & Sales plans.

I assume 25% off almost $15k annual with pretty much zero CAC is not far off from what HubSpot sales would offer themselves to a multi-year deal.

We're bootstrapped, all-in on AWS and have our $25k expiring soon.

We saw it advertised as 90% off on a startup platform we're part of, applied, and we were told since we're a bootstrapped business and haven't raised any money, we can only get 30% off.

It left a sour taste in my mouth.

If you're bootstrapping a business counting every penny of your own money, you're at disadvantage, but if you raised $2 million, we're happy to save some of your VC money!

¯\_(ツ)_/¯

I hate holding anything since iPhone 12 in my hands, the edges are sharp and cut into your fingers.

Every time I take iPhone X I'm just amazed how comfortable it is and what a step back was the iPhone 12 design.

It sounds personal for you.

React is more popular than Ember.js will ever be.

However this is apples to oranges, one is a view library, the other one is a batteries included framework.

I think you're a little out of touch if you honestly believe Ember and especially Ruby on Rails are legacy products. We have multibillion tech companies shipping 10+ years old existing apps and building new apps in both of these frameworks.

This mindset of branding stuff "legacy" because it's not trendy on Twitter or reddit is one of many reasons why JavaScript fatigue exists.

All while Ruby on Rails developers are one of the most happiest and productive web developers shipping stuff because they don't need to reinvent the wheel and solve problems that have been solved a decade ago. (p.s. I've never done RoR, I just understand what convention over configuration does to developer productivity)

If you want recent examples, go look at Apple TV web[1] built in Ember (even though I personally wouldn't use Ember for such a project) or Hashicorp building all their products in Ember and releasing their new Helios design system[2] in Ember just few months ago.

Again, these examples don't matter.

I've hired full-stack JavaScript developers, I couldn't care less if they've done React, Ember, Angular, Vue, Svelte or whatnot.

Because it'll take any proficient JavaScript developer a week or two to understand the concepts and structure of any framework or library above. They all do the same thing - render pages and wire up buttons to run network requests, I don't understand why people make it sound knowing React, Vue or Ember is equivalent to knowing C++.

It's all JavaScript doing the same thing slightly differently.

> What has Ember done but continually play catch up for years and years on end?

You can find your answer here https://www.intercom.com/blog/evolution-of-ember-at-intercom....

> How many years do you have to scroll back to find anything that influenced anything outside of Ember?

I can tell you about ember-fastboot, ember-engines, miragejs, glimmer vm, i18n, accessibility and other things Ember and Ember community have done to SPAs in the last 15 years, but again, why does it matter right now?

Stop measuring who's done more. There's nothing I can tell you that will change your mind, just enjoy whatever you use now.

All the best <3

[1] https://tv.apple.com

[2] https://www.hashicorp.com/blog/introducing-helios-hashicorp-...

Neither will ever be popular.

Because it's always be easier to learn and spin-up an Express.js or any front-end library with a single index.html and tinker away.

> than into doing anything relevant outside the Ember community in the last decade.

Quite dishonest, and not sure why you're turning this into measuring exercise, so I won't bite.

> Might as well have said Dojo and Knockout, it would have meant the same thing.

Someone should tell Apple, HashiCorp, DigitalOcean and Microsoft they're not cool anymore releasing new stuff in Ember.js, must pick a new JavaScript framework of the year!

Ember.js and Angular.

And I wouldn't call React a framework, it's a view library.

Let me explain.

While there was a new React router coming out every week in early 2010s, some teams picked a batteries included framework such as Ember.js and focused on productivity and shipping rather than bikeshedding which router to use or what folder structure to have.

And those teams have been upgrading their apps for over a decade since the early Ember.js versions (some even upgraded from before Ember was forked from Apple's SproutCore).

Intercom swears by it https://www.intercom.com/blog/evolution-of-ember-at-intercom...

So do some Ember apps at Apple, LinkedIn, Microsoft and Heroku that have been going through this journey for years.

And they will carry on.

There's a new and faster rendering library out on the block?

That's easy. We'll just replace the rendering engine.

That's what Ember.js did in mid-late 2010s with Glimmer.js, where they dropped-in a complete replacement of Ember.js rendering engine with full backwards compatibility which was beating React in some benchmarks.

https://auth0.com/blog/face-off-virtual-dom-vs-incremental-d...

So frameworks such as Ember.js, Ruby on Rails and others will still be there in 15 years, alive, with people interested in productivity rather than tinkering keeping them fresh and alive.

View libraries? Yes, but in the same sense jQuery is today. It's there, it's being patched, thousands of sites use it, but there'll be better ways to do it.