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.
108 karma · joined December 26, 2012
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.
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 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.
If you're comparing it to ReasonReact, you still have the React/ReactDOM Javascript dependency which is still ~30kb gzipped
I like Datagrip as well but it has too many features for me since most of my queries are just SELECT's with maybe a JOIN.
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?
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.
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.
I'm looking to get an Amiga mainly to run Octamed and get that Paula chip sound. Can someone suggest a model to buy?
1. Miami Bass & Bounce
All the songs in this playlist are Miami bass songs. There are no bounce songs. At least add The Showboys - Drag Rap on there.
2. Southern Rap & Crunk
You can't roll this up all into 1 section IMO. To make this point, there is not a single Cash Money Records/No Limit Records song in the playlist. If you don't think they deserve their own tree, look at their record sales. I would argue that the descendent tree (Trap), is more influenced Cash Money and No Limit than crunk.
N.E.R.D. - Lapdance is in the playlist. I think this is a big stretch. Yes, I know Virginia is technically in the South but their sound is nothing close to it.
3. Grime (listed with Breakbeat Garage)
This deserves its own tree. Grime has been starting to gain major traction outside of the UK as of late. Also, current day Grime is heavily influenced by trap/drill.
and 1 minor nitpick not rap related - Juke(ghetto house, ghetto tech) is influenced by Jungle. You'll hear sped up breaks in quite a few of DJ Rashad's songs.
$ npm install --save react react-dom
$ npm install --save-dev webpack webpack-dev-server babel-core babel-preset-es2015 babel-preset-react react-addons-test-utils
/webpack.config.js module.exports = {
entry: 'src/index.js',
output: 'dist/bundle.js',
module: {
loaders: [{
test: /\.jsx?$/,
exclude: /node_modules/,
loader: 'babel',
query: {
presets: ['es2015', 'react']
}
}]
}
}
/src/index.js import React from 'react';
import ReactDOM from 'react-dom';
const MyRootComponent = (props) => {
return <div>Hello World</div>
};
ReactDOM.render(MyRootComponent, document.getElementById('react-app'));
/static/index.html ...
<body>
<div id="react-app"></div>
<script src="bundle.js"></script>
<body>
...
start the web server $ webpack-dev-server --content-base static/
There is nothing forcing you to use all the extra dependencies. You can build a full app without them.I've built some complex UI's with the same class name styles (Basscss). 99% of the time I'm reusing classes and I don't have to write anything custom.
Prototyping is great once you memorize the classnames.. Just write HTML, no need to switch to CSS files.
If you're working with global styles this is by far the most scalable CSS methodology as of right now IMO.
What reasons are you're dropping your old libraries/frameworks in favor of the new ones?
If an unstable API is a big problem for your use case, why not just stick with the old library or just not update the dependencies?