Interesting reading, I share some of the points in the post, however, one more dependency manager?
Mostly I've used plain `python -m venv venv` and it always worked well. A downside - you need to add a few bash scripts to automate typical workflow for your teammates.
Another point is that it does not work well with PyCharm and does not allow to put all dependencies into the project folder as I used to do with venv. (just like to keep everything in one folder to clean up it easily)
Are there any better practices to make life easier?
Actually, I recommend bash scripts for automating team workflows as a best practice.
You create a wrapper script around your application that calls a dev environment set-up script, that [if it wasn't done yet] sets up the environment from scratch for that project or application, and loads it before running your application. This does a couple things.
First, it removes the need to train anyone on using your best practices. The process is already enshrined in a version-controlled executable that anyone can run. You don't even need to 'install lore' or 'install pipenv' - you just run your app. If you need to add documentation, you add comments to the script.
Second, there's no need for anyone to set up an environment - the script does it for you. Either set up your scripts to go through all the hoops to set up a local environment with all dependencies, or track all your development in a Docker image or Dockerfile. The environment's state is tracked by committing both the process scripts and a file with pinned versions of dependencies (as well as the unpinned versions of the requirements so you can occasionally get just the latest dependencies).
Third, the pre-rolled dev environment and executable makes your CI-CD processes seamless. You don't need to "set up" a CI-CD environment to run your app. Just check out the code and run the application script. This also ensures your dev environment setup scripts are always working, because if they aren't, your CI-CD builds fail. Since you version controlled the process, your builds are now more reproducible.
All this can be language-agnostic and platform-agnostic. You can use a tool like Pipenv to save some steps, but you do not need to. A bash script that calls virtualenv and pip, and a file with frozen requires, does 99% of what most people need. You can also use pyenv to track and use the same python version.
Every time I saw simple bash scripts or/and Makefile used - it did not seem to be the idiomatic way of doing things in python but after using it for a while - turned out to be one of the best development experiences.
> Another point is that it does not work well with PyCharm and does not allow to put all dependencies into the project folder as I used to do with venv.
This is annoying for AWS lambdas too, because you have to bundle the dependencies and zip it. It's pretty trivial to go Pipfile -> requirements.txt -> pip install -t if you use a Makefile, but it's definitely an omission. I asked about it on their github though and it is a known issue, hopefully it'll be there soon.
> because you have to bundle the dependencies and zip it
btw, I've used serverless to deploy lambdas in python and it worked super cool. Highly recommended.
> I dont have the patience or the know-how to tune the touchpad to be decent in Linux.
I thought it would be an issue too, however Gnome and latest ubuntu fixed issues with trackpad and screen resolution
It takes a few hours for me to switch to any OS. Most of my tools are not OS dependent like (vim, PyCharm, Chrome/Firefox, Sublime), others are default ones (I do not really care which shell script is there or which tool to use to read my emails or store passwords, there are a lot of alternatives)
I guess if you do video editing or staff like that XPS or any other machine is not an option over MBP
Good summary, I share most of the points provided in the post.
Also, I think a few more things worth to mention.
Pros:
- XPS has a decent hardware (I got 16GB, i8Gen, 500GB SSD and forgot about having a few docker containers running on the background which was an issue with my MacBook Pro 15 (8GB, 2.5Gh)
- It is really 1k$ cheaper than the same config MacBook model. Apple's Retina and Touchbar are really cool, however, they still do not have 16GB 13' mac which is a deal breaker.
- Touchscreen. Take your touch bar and put it into your missing 3.5 jack plug, Tim's Team, why would I need a touch bar when I have a touchscreen; (no offense to Apple, I still own a few apples because they are nice)
- the webcam is well described, but it is not that bad, it saves a few inches in size which makes its screen look like it takes all space and there are no borders at all;
- while ubuntu became usable with Gnome desktop I almost did not notice all missing Apple's out of the box features;
- it is very light (~1kg), my backpack can be heavier;
Cons:
- WiFi is super shitty in XPS series. If you have not had any issues yet - then you have not bought one yet. It is better to replace with 30$ adapter to not have issues with differently configured routers;
- It has Windows on it and some features are not supported on Linux. For instance, I see no sense in having fingerprint scanner if it does not work under Linux;
- Be aware that screen scaling might not work on some linux machines. For ubuntu 16.04 I got windows so small so I cannot read the text. Luckily 18.04 fixed it, but still;
Overall, it is the best laptop for Linux I've used so far (Lenovo and Asus are good ones as well), having good hardware and being more or less cheap. I hope Apple will simplify ML and add a bit more RAM to Autumn's laptops, otherwise, there are no reasons to go back.
Holy cow, yes. My wife's XPS 13 had the crappiest Killer WiFi card, and Dell would not acknolwedge that it was the source of all of our issues no matter what I tried, no matter what evidence I presented. The WiFi card was causing all sorts of issues from slow browsing, to the entire computer freezing on restart/shutdown, to no WiFi after wake up from sleep... the list goes on.
I finally rage quit after a session with Dell support had me run hours of meaningless diagnostics tools and then said everything was ok and to check my router. I told them right from the get go that I suspected the Killer WiFi card was faulty, but the technicians always ignored that piece of info.
I bought an Intel 8265 to replace the Killer WiFi card, and when I went to replace it, the antenna ball broke off of the Killer card and was stuck inside the little socket! There was a tiny flake of solder I was able to grab with my finest pliers and pull it out, allowing me to install the Intel card. After installing the Intel card EVERY SINGLE PROBLEM described earlier went away.
$30 was all it would have taken to make the XPS 13 from a piece of garbage to an awesome laptop. I'm already paying $1000+, why not $1030+? But now, I will never buy another XPS again because it required 10+ hours of my time to troubleshoot and fix all by myself.
> and forgot about having a few docker containers running on the background which was an issue with my MacBook Pro 15 (8GB, 2.5Gh)
It's almost as if Docker has to start and run in a VM on non-Linux systems.
> however, they still do not have 16GB 13' mac which is a deal breaker.
What are you talking about? You've been able to upgrade the memory in a 13 inch MBP to 16GB on purchase since like 2015 at least
> Touchscreen
I've had two traditional laptops with touchscreens. Both times they got in my way and I stop using the touchscreen after like three months max.
On a 2-in-1 like the Surface Book where touch is a first-class input it's a completely different story, but on traditional laptops a touchscreen is far from an ideal user input device. It's like the N64 controller - you're left wondering if the manufacturer thinks you have a third arm coming out of your chest or something. To use it you have to take your hand completely off one of your two much better input devices (keyboard and trackpad/mouse) and hold your arm in an awkward, quickly painful position if your laptop is in a normal position (on a fairly flat surface with the screen straight or maybe tilted back a little, a couple of feet away from you max). The touch bar isn't the greatest design decision but moving a finger up to tap e.g. the bookmark app control in Chrome is a far more natural movement than lifting my hand to the screen to attempt to poke at the bookmark star which is rendered at like half the size of my fingertip.
> It's almost as if Docker has to start and run in a VM on non-Linux systems.
Just as an FYI, that's no longer true for both macOS (xhyve) and Windows (unknown underlying tech, but compiling and running dockerd behaved reasonably with the exception that one could only run Windows docker images). In fact, IIRC, even Docker for Mac uses xhyve, so only docker-machine folks use the VM-based solution
Realistically, it is still true on Windows - unless your containers don't need chmod, chown or any of the other rather fundamental syscalls that are still not supported under LCOW
I also used an XPS 15 for personal and work before switching to a Macbook, and it was also much thicker than a retina MBP. I didn't have a touchscreen model, but the touchpad was probably the best touchpad I have used on a windows machine (it even had good gesture support, like 4 finger swipe to switch programs). It did have some weird quirks like the optical drive would make a loud mechanical noise whenever you turned it on, and the screen would often get dust stuck behind it which was basically impossible to clean.
By the way, all Macbook pro models still have the 3.5mm audio jack.
I have XPS13 with Killer wifi (Atheros QCA6174). At first there were stability problems but they were completely solved with FW update from Atheros's github repo and a kernel update (to >= 4.9 I think).
Later it turned out that an Intel 8260 card I've bought to use in PC-based AP cannot be coerced to work in 5GHz band no matter what I did, so I've swapped them, now Atheros is in AP and Intel is in XPS, with everything working flawlessly. So it turned out that the Intel card is less functional...
>"WiFi is super shitty in XPS series. If you have not had any issues yet - than you have not bought one yet. It is better to replace with 30$ adapter to not have issues with differently configured routers;"
This is really surprising. Can you say what specific replacement worked for you on that laptop?
The 9343 model shipped with a Broadcom wifi card, which was a PITA to get working on Linux. I swapped mine out for an Intel 7265, which has kernel support, so, any distro I throw on there works instantly without having to download a bunch of drivers.
More recent models have switched to the "Killer" brand wifi card, and I'm not sure whether those have in-kernel support or if it's another akmod thing.
Yeah, it was nice for a first few weeks and when I went travelling I got into issues. Some WiFi's did not work and a guy with a MBP next to me was just smiling :D
Just google for XPS WiFi issue and you will get plenty of results. This model should be a good fit: Intel 8265 Generic, 2230, 2x2 AC+BT (8265NGWMG), look for Intel wifi cards they are much much better than default ones.
Wifi hw is also an issue for surface pro 4 (under windows and Linux both). Apparently ms finally fixed in the 5th generation.
Anyone know if there's any really great wifi cards internal or USB, that allows full AP, "war driving" etc - and also 5ghz and such? Preferably with great drivers for Linux and freebsd?
(I doubt internal is an option for my surface pro 4, but for refurbished ThinkPads/dells it might do the trick..)
XPS's Atheros QCA6174 works fine with recent FW. I use it in AP mode in 5GHz band in ac mode, though I had to adapt a kernel patch from OpenWRT that ignores frequency regdomains. I've also tried to use Intel 8260 for this, but with no luck.
I also have the XPS and have experienced my WiFi dropping. Usually a few times a week. I've heard you can contact Dell support and they will send you a wifi adapter but I haven't tried it yet myself. Curious to hear of specific replacement options too.
I had massive issues with the Killer Wifi until I installed an (April 2018 iirc?) driver update from the Dell website. Dell's update tool didn't seem to install it.
That stinks. You would think a decent wifi chipset would be a solved problem in 2018. Especially from a company that has been shipping laptops for as long as Dell has.
I need RAM, battery life, and a matte display above everything else, so it really bothers me that Dell refuses to sell a 16GB XPS13 with the 1080p display.
So much so, that I think I'm going to go with Asus for my next ultrabook.
Removing the 3.5mm jack from phones was an exasperating way to push air pods, but they didn’t do the same thing to their laptops. You can plug headphones into the latest MacBook Pros without any sort of adapter.
Agree, moved to tap-click in a first day. As time goes you get use to it but it is still far from Mac touchpad (even more I have not seen anything better in any laptops)
Can't speak to the XPS 13, but on the HP Spectre x360 13", I can click, without undue pressure, anywhere except when my finger is literally touching the top edge of the trackpad. I have the same experience on my 2014 Retina MBP, too. I feel like you might be overstating the benefits (which exist, but IMO are not that big) of the non-mechanical touchpad just a little.
Maybe you're right, but for me it was a little jarring at first.
Little things like that add up - and it's nice when they are just completely out of the way. FWIW I don't have the issue you reported, I can click anywhere on the trackpad, even the very edge. Mostly useful when you're dragging and dropping or selecting text etc.
Especially using "comics" style as it was mentioned before. Not only colours on data structures help to understand the algorithm, but also those nice tips, lamps and stars here and there. You might call it childish, however as a student or a child I would rather read a book like that than a typical linux manual like book.
Here is what I would be looking for on top of this idea (which is awesome):
- A full list of algorithms from "Introduction to Algorithms" by T. Cormen;
- A colored mark on algorithms types depending on a problem, let's say search - green (the greener - the more efficient it is), graphs - blue and so on. The reason I would like to see it is that it is much easier to look for an algorithm if I know the color, so I just match the color going through pages;
Thanks a lot for the suggestions! I'm not quite catching what you mean by color-marking algorithm types... would you be willing to email me and chat about it? I think it sounds cool. You can reach me at levi ..at.. coderscoloringbook.com
I have been using vim as my primary IDE for small projects for more than a year till previous month. Everything was fine, even optimizing slow plugins was OK for me. The best plugin I used was a YCM, the best autocomplete I've seen in console world, and there were so many problems with it.
Finally I gave up and moved to NeoVim and have no issues with my vim anymore. Maybe later I will give another try to spacevim or emacs. Maybe. So far, keeping my fingers safe :D
