I always reach for django for new projects. It's never let me down and can be used in many, many ways.
I usually end up with fairly succinct code and it's never difficult coming back to a project that is 5-6 years old. Can always understand what's going on in the project and get my mind back and running quickly with it.
Using it with GraphQL (graphene) makes it feels a bit more like one of the newer frameworks out there.
Really happy I learned it years and years ago. Nice to invest time into a framework that is still going strong so many years later.
It's back now. Definitely worth a look. Been using bitwig for ages as it works beautifully on Linux and I'm really excited about version 3. Nice to see the project progress in such an amazing way.
It almost doesn't matter. Do you remember the hours and hours spent trying to debug something on IE that worked perfectly on Chrome/Firefox/Safari? All because MS didn't follow the standards that everyone was getting used to and had (mostly) advocated?
The thought of having to do anything remotely similar to that makes me shiver. Since MS made me go through that years ago, I simply will not go through that again. They did such a poor job with IE and it takes time for wounds to heal. Might sound a bit pathetic, but working life without having to develop for IE is much nicer. Chrome, Firefox and Safari generally behave in a similar manner. Yes, there are some inconsistencies, but nothing like IE. Especially the earlier versions (6!).
Really not sure this is an alternative to blender. Blenders functionality stretches way way further than this. Go check out the blender 2.8. I think you'll be really quite impressed by the improvements that have gone into it.
Blender might be a "nightmare" for you. But without putting any proper criticism, your point is null.
This is it. Safari really doesn't compare to chrome/firefox in terms of good developer tools. They are there, but no where near as useful/powerful.
I have noticed a few quirks in Safari that I have to work around. Like not rendering things exactly the same way as chrome/firefox. Bit of a pain, but there is never anything that's really "broken".
Really great advice here. Sometimes might feel a bit stupid having all that equipment for a relatively short journey, but so worth it when you do need it.
I've got a little 13" XPS Developer Edition and it's a really solid option. The build quality is perfect and I've yet to come across any issues with it. Use daily for web development in work and for personal projects.
With an i7 it runs really smooth. I opted for the FHD option for the longer battery life, but would have gone UHD if I didn't mind about battery life.
It's really nice to see Dell make Linux part of it's line-up. Part of me bought it as a little heads-up to Dell that Linux laptops are a good thing. I've always just installed Ubuntu over existing windows laptops, but it's nice to see it somewhat as a first class citizen with Dell.
Good god I owe you a beer. I am able to live a very nice life developing with django. Working on a large(ish) system with django, and it's an absolute joy. Thanks to you and everyone who has contributed.
Yea I'm big fan of it. Strange things used to happen with npm, dependencies would break, installs would fail etc... Maybe something to do with our build config, but since moving to yarn, no problems. We don't ever think about packages breaking or anything now (which is how it should be).
I was part of a team developing a travel product which needed huge amounts of data from flights to car rental... My god the travel industry is a mess in terms of accessible data. It was the biggest pain point. API's would randomly change structure, endpoints would stop working with unknown errors, data would be significantly different across companies for the same data etc... It was a shambles. Never again will I develop in the travel industry. Unless you own the data, working with it is terrible.
We ended up building our own little system that merged our own flight data with data from suppliers. The schema some of the suppliers provided was non sensical and it ended up being a really finely tuned system that would break reguarly if one of the data suppliers decided to change it without notice.
I spent my days dreaming of a standardized data pool, and while some of the data was standardized, not enough of it was.
Thank goodness I'm now working in an industry that we can totally own our data and are not reliant on anyone else for it.
Interestingly, django-webpack-loader has completely replaced django-compressor and all the other static bundlers. I like how configurable webpack is and how much control it gives you.
Anyone else completely switched over? Every single static file runs through webpack for me now, and I couldn't imagine ever going back.
Django Rest Framework is one of the reasons i use django so much. It is done in a really solid way, allowing great power and flexibility over how you want to abstract your rest API. I've used tastypie before, but got the feeling it wasn't as fleshed out as DRF. I remember coming across strange behaviour with complex nested data. Moving over to DRF empowered me.
Most of this is to do with the customer support, and not really about the actual laptop. But... It is annoying when things go wrong and you have to deal with poor customer service and you feel like you are constantly battling the company.
I've had a little Dell XPS 13 Dev edition and I really really like it. Everything works well, it's fast, it's got a good display and it stays out of my way and allows me to fully focus on work. I've added gestures on the trackpad to act similar to OSX as I got used to them on my Macbook. Nothing really special to this laptop, but it's damn good and has been behaving itself.
Great link. Just finished reading through it and I feel more educated on typography. At the very least I now have a better feel of the lingo and vocabulary which surrounds typography. Thanks.
This really isn't why the JavaScript community is fucked. It's just a reference project for others to learn from. The spreading of information and ideas through code doesn't mean anyone's fucked. Why fucked? Are you reading into the fact that it's a young ecosystem with a turbulent flow at the moment? JS is just finding its groove. It's an always developing language that has the difficult job of being the language that runs on a fuck load of systems, within the enormities of the internet.
I usually end up with fairly succinct code and it's never difficult coming back to a project that is 5-6 years old. Can always understand what's going on in the project and get my mind back and running quickly with it.
Using it with GraphQL (graphene) makes it feels a bit more like one of the newer frameworks out there.
Really happy I learned it years and years ago. Nice to invest time into a framework that is still going strong so many years later.