Both Catalina and Mojave were the smoothest MacOS upgrades I've had for a very long time.
The only issue I have with Catalina is that I can't figure out how to disable password auth for sshd since the config is basically read only now. Ended up using Wireguard and disabling external SSH access.
Not exactly unhappy but why vanilla? By using transpiler and bundler, you get to,
- Use better JS (TypeScript) to be sent as ES5 (down to IE6 supoort) without waiting for people to upgrade their browsers to the latest, which is forever.
- Upgrade to latest specified version of libraries without having have to check every site and download the min.js or change the script tag url manually and dependencies are resolved automatically.
- Get to use stuff like stylus which is already far better than CSS 3 syntax and again, no need to wait for people to upgrade their browsers.
- Bundle all JS and CSS as a single file (and place all the other assets like images at a specified location automatically), which can be cached for instant load from second page, unless your frontend code is so fat, a single file becomes too huge for it.
- If your server side is node.js, you get to use a completely same language (TypeScript) for backend and frontend.
The problem is one of culture. A reliance on complicated tooling requires specialization to these tools, which slows down team building time.
I've rescued several projects where more time was spent on making the lives of the developers "easier" than actually solving the problems of the user. Bike shedding and navel gazing is a huge problem in our industry, even if we don't like to admit it.
If you build components that use other components, without using a bundler, you constantly have to remember/know what uses what to get things to load. This may sound like not a big deal, but it doesnt take long at all and suddenly you've got loading issues!
I’ve been using utility classes for a few years now. Some thoughts I’ve come up with:
For content heavy sites like ecommerce/marketing/blogs, I use pretty much utility classes exclusively. There usually isn’t much reuse of UI components on these types of sites so maintenance is much simpler compared to semantic classes. With semantic classes you’ll have a lot of one off styles.
I actually really enjoy writing sites like these since I can code a site start to finish without touching any CSS files. Using utility classes I probably finish 25%-50% faster than if I were to use semantic classes.
On more web app type things like admin panels, I use a mix of mostly semantic classes and a few utility classes. I only use utilities to make sure there aren’t a million different padding/margin/font size values.
In the earlier days of React I tried using all utility classes and it just felt like there was too much going on in the JSX. If you use utility classes, you know the class attribute can get pretty long - sometimes needing to be broken into 2 lines. The CSS tooling with Webpack has come a long way and solves a lot of the problems that all the utility class frameworks were trying to solve around 2015.
I've been working with Shopify for close to 10 years as an owner of multiple profitable stores and as a full stack developer. If you work on the custom development side you'll see a lot more successful businesses run on Shopify.
I don't see the churn rate as a big problem for Shopify. Their revenue is pretty tied into the customer's revenue and expenses, not the amount of unique subscriptions. On top of subscription revenue, they have credit card processing and shipping labels which would be higher than the subscription cost for shops with high revenue.
IMO I don't really see Shopify and Amazon as really being in the same space unless Amazon makes a real push into curation and I think that would require a radical change in how Amazon works with sellers. I see Amazon as more of a competitor to Walmart, Target, etc.
I built a hackintosh using the recommended build and had a mediocre experience. Things I take for granted like sleep and Bluetooth were broken. I ended up spending weeks trying to fix it. Eventually I gave up and bought Apple hardware which hasn’t been perfect, but it’s definitely less annoying than the hackintosh.
Question for Vue users: whats the value prop over React?
I haven't had a chance to look at Vue in depth but it seems to me that its useful for building apps where you don't need a build tool which makes sense to me.
The main thing I don't get is why use Vue over React if you're going to use single file components with some kind of build tool?
> Question for Vue users: whats the value prop over React?
I'll paste my comment from another post in this thread:
>> I hear a lot that "Vue is easy to learn"...
> That's why I started working with Vue. It seemed easier to approach for someone coming from a server-side language perspective (I'd mostly worked with Python/Flask and PHP/Symfony before). I could slowly ease into using pieces of it until I learned enough to write a whole project in Vue. You can probably do the same thing in React, but the Vue docs were written to address my use case.
Expanding on what other people have said with some anecdotes:
Most developers who don't have operational experience of a ecommerce business will recommend some kind of open source cart. If they're in the WordPress community they'll recommend Woocommerce. If they're used to building web apps they'll recommend something built on top of their framework of choice.
Almost everyone who has experience working on a successful ecommerce business will tell you to use Shopify. It has all the basic tools you need to run a successful store. If your store is a failure on Shopify, then it would probably be a multitude worse on a custom built cart.
As stated in other comments, the actual cart is a cost center in a ecommerce business. There are stores using themes with minimal modifications doing millions in sales. On the contrary, you could have the most well built site and still have no sales.
If you want to put your technological skills to use, use it on things that generate traffic like content or marketing.
Record labels are already in a dynamic where the streaming services have at least equal leverage. Playlists are already taking over radio which is where the labels would give you the most value.
More artists are publishing their music independently. I think the negotiation power of older records owned by record labels will diminish because the next generation of independently owned records will outweigh them.
The thing I'm unsure of is how Apple Music vs Spotify is going to play out. I feel that Spotify is currently an overall better product but Apple has had major cultural impact with its curation which IMO is more valuable than building software.
The only issue I have with Catalina is that I can't figure out how to disable password auth for sshd since the config is basically read only now. Ended up using Wireguard and disabling external SSH access.