sic1
I have minimal plugins, but have once again removed some more that I thought were helpful, performance got a little bit better again. But we shall see how long it holds up, as I've done this a couple times now in an attempt to gain reliable performance. This is on basically a brand new 15" i9 Intel MBP.
I'm not the only one I've talked to that has random slow-downs like this. I've literally contemplated going back to Sublime Text 2 for my sanity - I just want things to work reliably. Oh, and if you accidentally click on one of your build files, enjoy the system lock-up!
I don't need new features every month in VS Code that I won't use. I just want better performance on the basics so I can get back to being in flow, writing code, solving problems.
Are you building in a react environment? Are you building WordPress websites? Are you just building simple landing pages? Are you building in a team environment? These could all have different solutions, they could also use similar solutions.
But you need to decide how you want to think about CSS. Which to me, is atomic vs component driven.
Atomic is building small reusable classes, then use those classes everywhere in your HTML. It keeps things consistent. [Tailwind CSS](https://tailwindcss.com/) is the winner of this race at the moment. Lots of people are moving to it. There are solutions for standard CSS, SCSS, or even working with it in React type environments.
Component driven is how I think of BEM, "Block Element Modifier". Break things into reusable components, keep your naming structure consistent according to BEM specs.
I personally prefer BEM type of process (break your pieces into components), but with usage of utility classes also, these can be thought of as atomic (one use, like text-align: center;).
I'm going to try Tailwind on a project soon (I've been following it for years), but I will still think of it in a BEM type structure. Things get messy in atomic when you have complex UIs that have different needs across device sizes. I personally have a hard time looking at HTML when one element could have 10+ classes on it if you go pure atomic.
I've kept things consistent without Tailwind with my own set of config (for things like colors, units, font stacks, z-index stack, etc), then various helper functions for things like keeping breakpoints consistent.
There are lots of great resources (look up atomic css and BEM css), you should browse through many of them to get a well rounded picture of how people work with CSS.
But figuring out how you want to think about CSS and putting a system around it seems like where you are. I recommend trying various methods out, and see what works best for you. Just be flexible if you are in a team environment. A team sticking to a defined standard (even if it isn't your favorite) is better than lots of competing standards.
I did however do what others are suggesting. I installed Signal, and told my close family and friends to install it to communicate with me - and to not use standard SMS anymore.
While I did get a bit of grief over it initially, we are all happily using Signal now, and more people I know are moving to it all the time.
It's also a great middle ground for iPhone and Android users to communicate.
However, I must say, it's 2019, if you call yourself a front-end developer, and you do not know flexbox and grid - you are greatly missing out on an amazing radical change in how you think about and design your layouts. There really is no excuse for not knowing this stuff, especially with all the great resources out there to help you learn.
Flexbox Zombies basically changed my life. It taught me the possibilities, and now I know them by hand. https://mastery.games/p/flexbox-zombies
The same company has a paid game to learn about the grid (https://gridcritters.com/), but I came across the resources below and did not buy it.
Flexbox Froggy and Grid Garden are both free, not gated by an email signup, and very high quality. You and everyone on your team should do them, even if you think you know them well. It will help with reinforcement.
- https://flexboxfroggy.com/ - https://cssgridgarden.com/
I think Gimli is an amazing tool, and I might even buy it when it comes out. But please, do yourself and your team a favor - learn the tools by hand first. If you wrote a float at all this year, this post goes out to you.
Programming proficiency and programming/development/software knowledge are two different things. He may have _proficiency_, but does he have real world experience of working in a dev team? Handling nasty bugs? Working on legacy code bases? And so on..
People may be able to get up to speed quickly with all the resources at their fingertips these days (which is great), but if you only had a team of those people... Well, I wouldn't bet a business on it.
Full disclosure, we just hired a 40+ dev and could not be happier with the experience he brings to the team. Yes, we could have saved $20K+ and got someone younger in their career, but he's already shown his value in getting up to speed quickly and tackling large tasks/issues right away.
There will always be shops on both sides of the hiring fence (I've seen both), I call them farm teams vs the big leagues.
That's a lot to bite off honestly. We have 80+ people in our slack account, but i'd maybe wanna use this for ~20 of them. Doesn't seem to support that type of deal though.
Yea, the class name should point you to the file you want to look at, but that is still manual legwork. And the whole atomic css-like pitch he has with the over-the-top `composes` functionality looks like its own nightmare.
I'll watch from over here and see if this pans out for ya'll.
Great content tho, enjoying the read.
Join up if you like bass music (dubstep, trap, future bass, glitch hop, chill bass, and the like) so we can test this with some dope tracks.
Either way, I started a room in http://jam.now.im/c/bass and its basically just bugged out. The track that i put in first (of course) is throwing a 500 when it tries to play `Failed to load resource: the server responded with a status of 500 (Internal Server Error)`.
You might need some sort of fail handler to ensure a room doesnt just get flat out bugged.
Either way, thanks, and I'll be watching closely :) Plans to open source? Or you more like planning to make $$? :P
Successful rants provide solutions at the end. Otherwise, its just that, a rant that has no real meaning at all other than allowing you to vent - like this post.
Feel better (I do).
But in terms of the web... if you can't create it with CSS3, its not worth it IMO. All those extra little shadows and light reflections... yeaaa. No thanks.
More designers should learn CSS and build out little things like this themselves so they can see how far they can take it without using an image.
You fetch your tweets from twitter, and build your html for them, position it out of view contained by an overflow hidden div. Go through the list of tweets, waiting a random amount of time to send them all off, and animate them from the bottom to top over another random amount of time. Im sure the biggest details will be in tweaking the timers so you get them firing off well. On animation callback, run the script again on the element.
Either way, fun game. Great work.
var Foo = function() {};
Foo.prototype.jump = function() {
return "I jump."
};
Foo.prototype.run = function() {
return "I run."
};
var mario = new Foo();
mario.run();
mario.jump();
Cool for the rubyist in you i guess. I just kinda go o_0
Desktop: Chrome, FF, IE 9+, Opera, Safari
Mobile: Android 3.0, FF Mobile 1.0, Opera Mobile, Safari Mobile 3.0.4+
Notable issues: No support for IE 7 or 8 (is there a polyfill?), No Android gingerbread support (a lot of people still have 2.3)
https://developer.mozilla.org/en-US/docs/SVG/Element/clipPat...
From there - getting this (beat pattern at the least) into something like Ableton (or some importable format beat format (does that even exist? (Inception!))) would be so awesome.
The biggest thing for me would be for it to be able to handle a pretty complicated rhythm. When i get goin, its a lot faster than your examples (and i'd imagine 2 notes hitting in the same place create a problem as well). I'd imagine it gets pretty complicated pretty quick.
Maybe even a way to record a beat, have it do the conversion, then record over it to make more complicated rhythms.
As you can see i'm excited about your product, and am probably getting way ahead of myself on some of the comments. But either way, keep it up, and let me know when i can try it myself. Thanks!
I still alias 'git' to 'g' also for all the other commands needed throughout the day. Not sure why yall would keep typing 'it'.
I do enjoy the ascii car tho. Cheers to that. Probably will set this up anyways!
> Any tool that appropriately allows for all this complexity to be specified, has already become as complex as CSS itself, thus defeating the purpose.
This was my immediate issue with CSS Hat. The designers are not trained to set up their photoshop files to be properly evaluated in CSS. They do not know CSS, or how it works. They get their pixels "perfect" (or way off most of the time when doing real math with css), but the fact is to use tools like this they have to get on board 100%. For some designers, this is easier than others.
Don't get me wrong, I'm still interested in trying out the tool. Maybe it is magic...
I am a coffeescripter, and i already have mixed emotions about the extra layer of complexity it puts on my code for others to get up to speed. Taking it further from the actual language (javascript) just adds a layer of obfuscation that does not really help javascript and its community at all (and many of the times your peers). It may make you feel better about what you are doing at the time (e.g. i must have typed vars, or whatever you people say), but its just making you feel better, it still is javascript, and you still have to debug javascript across browsers - that's just that. You still need to know all the javascript, you cant just use X to js and only know X. Only reason i get away with coffeescript is when i know im modern browser world, not old ie and the greater world of browser bugs. Otherwise im writing javascript.
app.trigger 'boom'
This lib (joosy) was built to satisfy your particular set of needs, and it seems that it does so well. Cheers to that.
_.throttle ->
console.log("Foo")
, 500
But hey, if you fork it, post the repo here! Ill help test it :)