The quality of what's being delivered since version 5 leaves a lot to be desired. They should really more people to their team and someone better since a lot of people depend on this code. Also, what's up them not understanding how semver works and releasing a pre-release code as the regular version. That's pretty basic man and rarely someone is OSS fucks up this badly actually.
dist-tags/release channels are far superior to classic semver pre-releases.
What is the difference between an unstable and a stable version? Testing by users. So as soon as enough users have tested / enough time has passed without issues, an unstable release becomes stable. In the best case nothing about the code needs to change, the release just needs to be promoted to the stable channel / dist-tag. That is pretty common practice for a lot of software and especially packages on npm.
With dist-tags, you can still make the versions meaningful. Between unstable versions, you can still express in semver terms what type of release it is (patch/minor/major). In classic prereleases, that is not possible. There is no semantic relationship expressed between a -alpha.1 and -alpha.2. Was it a bugfix? Does it add a feature? You don't know.
The issue is that npm did not mention in their blog post that 5.7 was released on the unstable `next` channel. The issue is not release channels in general.
> That is pretty common practice for a lot of software and especially packages on npm.
This is mostly what I have a problem with. Almost everyone is other ecosystems do not do something like this and there is a very good reason for it. Why not just follow a known and standard process of releasing things. https://twitter.com/maybekatz/status/966730802187792386
Even the NPM dev acknowledge the current process to be faulty and are considering switching to use pre-release tags.
I have been writing Django professionally since 2013, It's ain't that bad. Our codebase is huge & it never takes us more than 2 weeks to do it and lately, it has always gotten less and less. Wonder if the issue is with your codebase that it breaks so much on upgrades.
Python3 upgrade is a task, agreed. But it actually gives good returns. The language is nicer to write in and we even saved some memory and CPU on the same load after the upgrade. So highly recommended.
Well. I disagree that it is not a real thing. For better debugging, you need to know more what's behind the scenes. Personally, I have seen some of my colleagues struggling to find the cause or better architect the thing because most of the decision has been hidden/taken by the framework. Not saying, it's true for all Rails dev but for some beginners, it really bites them.
Sure but there is magic everywhere. You trade convenience for the risk of not knowing the underlying mechanism in action. The inverse is long boilerplate code, setting up multiple services and factories and fooWidget stuff just to do a simple thing. It’s more clear, yes, but is it always better?
Rhetorical question by the way... just food for thought. There is a balance. I happen to love the convention rails imposes and the “magic” it offers. That being said, there isn’t anything about it that I consider wizardry or don’t understand. It’s just ruby.
> The inverse is long boilerplate code, setting up multiple services and factories and fooWidget stuff just to do a simple thing
Are you not talking about Java here? ;)
Clearer code makes it easier to reason and hence easier debugging. Correct me if I am wrong.
Also, it really depends on person to person on how they write the code. Django does not mean big boilerplate nor does Rails.
My main question was on performance. How do they stack up next to each other? Python3 with Django is really working well these days. You can also check out the performance improvement on Instagram because of it. https://thenewstack.io/instagram-makes-smooth-move-python-3/
It does say that the 20 million lines statistic isn't sufficient to dismiss the idea. That's not saying much, but I think it's a valid response to someone pointing out that the Linux kernel is 20 million lines.
you're comparing apples and rutabagas. code line count is a hilariously inaccurate way to measure the complexity required for a portable OS kernel vs a userspace application.
> code line count is a hilariously inaccurate way to measure the complexity required for a portable OS kernel vs a userspace application
I never said that. My whole premise is that you can't say anything like this by just saying code count on two very different projects. Maybe you didn't read my comments properly.
What's the relation with Rust?
I don't see it mentioned in the post, it affects Firefox before version 57, but not 57 (not that there wasn't any Rust code in Firefox before 57) and it seems to be a bug in DOMParser, which as far as I know is not written in Rust.
Thanks for building a great editor that just works and is fast enough. It has the lowest barrier to entry and is mostly free due to unlimited trial. 5 years ago, when I started writing code professionally, Sublime made things so easy because I didn't have to learn an IDE to write code.
Many kudos and one day I will definitely buy a LICENSE.
I make enough to buy any damn License I want. I never said it was not justified. I don't use Sublime these days. I had fond memories of starting with Sublime and so I said and for the nostalgia sake, I will fucking buy the license as well. So stop assuming things and judging people, alright?
It happened to me when I was in the first year of my job. I was coding for 14 hrs straight for more than a year. I had a lot of websites that I needed to maintain and all the tech was new to me.
Then when burnout struck me hard, I realized that I just don't want to open my laptop anymore. Also, even side project started to feel like a burden to me.
Then I decided, enough is enough and I need to do some changes to my life.
- I did join a gym near my house.
- I stopped coding in evenings. I would wake up early and code for 2-3 hours in morning and be content with whatever I achieve during that time.
- Evening hours after office would be only for gym, relaxing, having dinner and watching TV.
Believe me, it was the best decision I did for myself. My health both mental and physical improved drastically and I started loving coding again.
Lots of great advice in these comments, including this one. I've also made a very conscious effort to keep my work from intruding on my personal life too much. Without that separation, one can burn out very quickly.
Also, I'm in agreement about the 2-3 hours of "golden" development, with the rest of the day for thinking, planning, or just doing something else. Sometimes I'm inclined to do 2 such sessions in one day, but a) I always make sure that the second session does not interrupt my sleep schedule, b) that I allow for plenty of down-time in-between, and c) that I don't do it for too many consecutive days.
