I think it's important for any comment or post touting the superiority of Vue to also provide insight into the author's experience with and feeings about React. You very rarely hear from devs who were loving React, tried Vue anyway, and came away believers. This leads me to wonder whether it's not so much that Vue is "better," it's more that it operates in paradigms that are intuitive to some individuals and teams in ways that React might not be. I don't see that as a hit against it or anyone but as a very satisfied React, it does make me take every glowing Vue writeup with a grain of salt.
To help put this in perspective, how heavily did you use React before switching to Vue? How did you feel about it at the time, before you were aware of Vue?
This is great advice, particularly the part about small, similar components instead of large, customizable ones. This is something I feel like I struggle with in views much more than I ever did working backend, and it's healthy to be reminded regularly.
On the subject of sagas, does anyone have a good solution for dealing with `call` in TypeScript without losing type safety?
This is all true for some languages but I think it it's far from universal. It seems to me that in many of the most frequently used and taught modern languages, the nearest most devs will come to being concerned with GC is an awareness of why object allocation should be minimized. For their purposes, that is a much better use of time than giving any consideration to GC tuning.
When I was trying to learn Rails, what differentiated Michael's book everything else I came across was his eagerness to not just show _what_ to do but also explain _why_ you're doing it. This is always my suggestion for anyone who is trying to get into Rails.
For companies managing the licenses for their employees, this is a great change. It's especially true for those who have a few primary languages but occasionally get contracts or have projects in other languages. For those with staff sizes in flux -- employees coming and going, contractors in and out, interns on board for part of the year -- only being responsible for the number of seats actively in use is extremely helpful, too.
Managing licenses for teams is time-consuming and frustrating. When I worked in the MSP world, convincing our clients (for whom we were essentially the IT department) that they had to buy an extra seat or upgrade everyone license or reminding them that, "No, you upgraded Sally to v5 but the Intern's system has last year's v4 license, and you have to shell out $X00 right now or they can't work" was a _constant_ issue. Creative Cloud and Office 360 made everything better, I expect this to have the same effect for dev teams.
I remember when the Storm came out. I was doing IT work for small businesses in the area and many of my clients, the Blackberry Faithful, would get their latest phones whenever possible. From the consumer side, it was every bit of the disaster this describes. The keyboard was an unbelievable disaster, it was horribly slow, crashes constantly, but they kept buying them. The Storm 2 was a relief, mostly because its improvements made my job so much easier.
What was always really interesting to me about Blackberry/RIM was how they managed to create some loyal fans who would happily follow their march into the sea. For years, even as iPhone and Android market share grew, there were (and probably still are) some power users who refused to even consider switching. These were exclusively owners or execs at small businesses, mostly companies with in-house Exchange servers that needed Blackberry Enterprise Servers. The BES always added an extra layer of pain for everyone, since we never got good enough with it to be anything more than a hornets' nest. Still, the Blackberry fans couldn't be swayed, called iPhones "toys," and insisted that their products were the magic to their productivity.
I appreciate a human, conversational approach to technical information and applaud you for your blog's tone. If you were writing for a professional news site it might be inappropriate but as a post on your own blog, you're entitled to whatever writing style you want.
This is a bit of the stretch. Philadelphia is a complex city with complex problems and its police department reflects this. It has plenty of problems but it also has a lot of cops who care.
I took part in a hackathon a few weeks ago and we needed a text editor that we could easily implement and customize. In particular, we wanted more control over the appearance of the toolbar -- we wanted to use our own buttons and move them vertically to the left of the text area -- and needed to capture events related to entering text.
We started with CKEditor, found it far too complicated and with a ton of old and unclear documentation floating around, and had to work against its default features to get it scaled back to the minimal editor we wanted. We weren't able to move the buttons to the left-hand side and couldn't style them as easily as we wanted to. Maybe it's buried deep in the docs somewhere but I couldn't tell you, there's a lot there and it's overwhelming for someone who's just getting started and on a time constraint.
Frustrated, we switched to WYSIHTML5 and were able to get exactly what we were looking for very quickly.
I've come to see CKEditor as the WordPress of WYSIWYG text editors: it aims to do ABSOLUTELY EVERYTHING for everyone, but that's not what everyone is looking for. Maybe things would have gone differently if we weren't under the gun but when we were in a pinch, we found WYSIHTML5 to be a much better option.
When I started looking through this, I wondered if any of the early-2000s adware platforms would make an appearance... and there it was! Gator at #17 in 2001. I was working at the tech bench at Best Buy in high school and removal of it and the other adware apps of that era must have been 75% of my job.
Did anyone ever spend much time with Light Table? I gave it a chance when the Ruby plugin was new but missed my Sublime plugins and shortcuts too much.
No, time that has passed is not a weak excuse if we are discussing something that is current and loosely involves many of us (the purchase of .io TLDs, an issue that only emerged recently) instead of having a general discussion about government abuses over time.
Nobody is trying to say that Native Americans didn't get a raw deal; only one person is trying to say that because Native Americans got a raw deal a few hundred years ago, it's OK to do the same to the Chagossians right now. This is the sort of logic people always employ when they're trying to feel better about participating in something shitty. It's the "But he hit me first!" of ethics.
This situation doesn't really seem like it's "history" in the same sense, considering it happened so recently, governments are still actively working against them as they attempt repatriation, and the TLD issue is fresh.
If nothing else, it would be nice if learning about this inspired those who own .io domains to contribute to a fund for the Chagossian people. I'd certainly match the $60 I paid to register my domain to a support organization if I could find one that looked legit.
Are they? I'm not so sure. They have a right to feel upset that money has disrupted (and not in some cool buzzword startup kind of way) their way of life by driving up the cost of living without trickling down to them. A lot of what was written struck me as sour grapes, frustration at the ease with which some people live while they slave away, but it doesn't change the fact that gentrification can destroy communities and culture.