Live data from Hacker News

Remix web framework aquired by Shopify

remix.run

111–120 of 209 posts

Re: Remix web framework aquired by Shopify

#111

Earlier quoted context omitted.

They are spending tens of millions building a ruby JIT so I am not sure you are painting an accurate picture here...

So they recognize they're having problems with speed. Dropbox also spent years trying to JIT Python faster with Pyston, and were unsuccessful. They now are leveraging Rust and Go instead.

how do you keep up with developments like this? I suddenly see how interested I am in what stacks companies are using and more so what are they going to be using in the near to mid term future.

Re: Remix web framework aquired by Shopify

#112
post #57

Earlier quoted context omitted.

because JQ is already loaded, and it IS minimal. You could do querySelector(...).addEventListener etc but why would you?

I get the purist push for Vanilla JS but for me it's still way too verbose. W3C has had decades to fix it and while it's improved it's still verbose as heck. Just implement the jQuery API into Vanilla JS and people would stop using jQuery.

That's what I did in Sciter:

1. Added element.$("selector") and element.$$("selector") functions. Later one allows to work with JQ sets:

     for(let el of parent.$$(".child"))
        ...
2. Added element.on("eventname" [,"selector"], handler) and element.off()

These two allow to reduce need for JQuery to almost zero.

Also added JSX as a built-in feature to JS/runtime. So,

     function Child(props) {
        return 

Generated child {props.index}

; } function Main() { const list = [1,2,3]; return { list.map( el => ) } } // add the list to the DOM: document.body.append();
These three simple things, together with elment.patch(...JSX...) eliminate need for as JQuery as ReactJS almost completely.

Re: Remix web framework aquired by Shopify

#113
post #72
post #70

Is Shopify shifting away from Rails?

This is something I'd like to know as well and nobody is talking about it, weird.

Remember the whining people don't take action .. but the guys who have been silent all along quit .. suddenly shocking everyone? They will keep saying everything is going great!

Re: Remix web framework aquired by Shopify

#114
post #22

Why acquire something that is MIT licensed? Is this really just a talent acquisition? https://github.com/remix-run/remix

I wouldn't really call it a talent acquisition. It's more the same reason that any company pays people to work on open source projects. For example, Google pays people to make Flutter and Dart. Are those employees a "talent acquisition"? Clearly no because they started the project within Google. So then why is Google paying people to work on some MIT licensed thing? Well, it gives them a high-quality bit of code to build the things that are actually their business and it gives them a certain amount of control over the direction and priorities of the project.

Let's say that I make a library X that your company uses. You can use X for free so why acquire X? Well, if X is a project of your company, that can give your company positive reputational benefits by association. You can set the priorities and roadmap of X. I'd be working at your company so I'd be there to help other developers. I'd see the friction you had in your environment and want to remove that friction.

I'm not saying that the owner of an MIT licensed project can do anything they want. There's always the possibility of forks. However, there is still a certain amount of control. For example, Google's control of Go basically meant that they controlled the decision to go with a non-copying garbage collector because that was what would be best for Google and its codebase (and most people wouldn't care about the trade-offs that much).

I think it's more than just "here are some smart people we can acquihire." I think it gives them influence over a project they might see as important.

Re: Remix web framework aquired by Shopify

#115
post #61

Earlier quoted context omitted.

Anyone remembers that upon Remix' initial release, one had to buy a licence for 250 USD? https://web.archive.org/web/20201204025307/https://remix.run...

Michael and Ryan have always been about trying to make money from their React expertise. They literally created a company called React Training: https://reacttraining.com/team and have had a fairly lucrative business doing workshops for years. No harm in trying to get folks to pay for a framework. It doesn't seem it worked, but I can't fault them for trying!

React Training worked really well, was very profitable till Covid shut it down. Obviously not a scalable startup type thing but still a nice little business.

Re: Remix web framework aquired by Shopify

#116

Earlier quoted context omitted.

Vercel already ate Remix’s lunch.

I was surprised how calm the remix developers reactions to the next 13 announcement were given how similar some of the new next features are. But now it makes sense! Upcoming acquisition on the horizon.

They already did some very public complaining about it several months ago when the Layouts RFC was first published.

Re: Remix web framework aquired by Shopify

#118

Earlier quoted context omitted.

I was surprised how calm the remix developers reactions to the next 13 announcement were given how similar some of the new next features are. But now it makes sense! Upcoming acquisition on the horizon.

Very related: https://twitter.com/ryanflorence/status/1587096603822673920 > Seeing that Next.js 13 preview before this acquisition would have put me in major defensive mode "HEY THATS OUR API" but now I'm just super chill and can work on Remix instead of my mental health

Because they cashed out, don't care anymore $_$. Looks like Shopify's diligence team should be blamed here.

Re: Remix web framework aquired by Shopify

#119
post #102

remix feels like the react version of htmx. I'd just use the latter, tbh.

I suspect you are confused about what Remix is, unless I vastly misunderstand htmx. By example, a request comes into my app's web server at `/posts/123`: how would htmx be involved at all in (1) understanding the request, and (2) generating the response? Remix isn't just client-side, it's also a server with routing and SSR.

Yes, the routing part isn’t covered by stock htmx but it can be shimmed server-side or client-side. The more “fundamental” bit as I understand it is that each logical/visible component is served by the server-side in a remix app as a separate, fully-rendered html component, instead of needing to render the entirety of the response to effectively obtain just a part of the view. Htmx provides that bit of the puzzle lending the remix-like aspect to a traditional server-side app.

Re: Remix web framework aquired by Shopify

#120

This is huge. Remix is my favorite React framework at the moment. It is by far the best abstraction I've seen of client/server model. Their API abstraction layer is just right, working with native browser and nodejs APIs, not obscure them. Typescript support is amazing. I'd bet my money on Remix model and direction vs Nextjs

Wait what? We have frameworks for frameworks now? What?? How did we get there :(
Post reply on HN