I had a similar thought until I actually started learning an instrument and my SO, flutist graduated from an Italian conservatory, made me start singing with the right intonation (singing the same notes you are playing on the instrument) and rhythm (division and subdivision alongside a metronome). Long story short: singing is hard and requires real effort. There is a good chance that what you think you can articulate is probably far away from minimal quality on both pitch and time.
Doctrine is deprecating YAML support. As you said docblock annotations are treated as default. I would like to add that this is so true by a large margin. To the extend that using alternatives feels like an (undocumented) extra step.
To clarify my previous statement: I like annotations. I just don't like how a large part of the community is forced into the docblock hack.
Every time I see an article about new features in PHP I search the page for the "annotation" keyword. To be honest I find it a little bit puzzling that to this day a large part of the ecosystem (Symfony, Doctrine, API Platform) revolves around docblock annotations.
Switch to Wayland or just enable TearFree on Xorg, something like:
`xrandr --output DisplayPort-0 --set TearFree on`
of course you have to adjust to your output (`xrandr --props`).
I am a full stack web developer using a Linux environment as my development environment. I plan to start learning some ML related stuff and I just recently bought a Radeon 5700 XT, the current high end consumer GPU from AMD. Before this I had an RX 580.
The driver support on Linux is fine but not optimal, there are multiple issues regarding color ranges, dual monitor support and with Navi based hardware (5700/5700XT) plain hardware freezes/hangs. I did not personally experience the hangs but I installed the 5.4-rc8 kernel and compiled mesa 20 from the git just to avoid them in the first place.
There is no Navi support on ROCm and the prefered way to have OpenCL on older hardware like Polaris (RX 580 for example) is to just extract the relevant files from the closed source driver.
I still prefer something with open source drivers but AMD is far behind NVIDIA in terms of GPGPU software support, I cant't honestly understand what their strategy is and why they are allowing the majority of developers to tie themself and their careers to NVIDIA.
I don't know, this is only my personal experience but every time I check .NET related stuff some Windows or Visual Studio related thing pops out and I think "nah, it's not worth it".
Not to sound negative but I can't really understand why they can't make their documentation platform agnostic like every other project on the planet.
Do you use Nvidia products on Linux? Reading "love" and "Nvidia" in the same sentence feels a little bit odd because the general sentiment for Nvidia on the Linux community is "don't touch it with a 10 foot pole". If I remember correctly Torvalds himself named it the worst hardware company they had to deal with.
Just upgraded from my old i5-4430 to the new 3700x. I'm very happy for the performance upgrade but there are a couple issues. I had to install Ubuntu using the netboot image because of the RDRAND bug affecting systemd. Systemd has already been patched with a workaround but the old one is hardcoded in the standard Ubuntu ISO. As usual the drivers for new hardware are lacking on Linux, as far as I know temperatures and fan controls are off the table until Linux 5.4.
As mush as I would like to switch to Firefox these results are very real, while doing frontend development with Angular or React the gap in Javascript performances is quite visible on every reload.
Last time I checked PHP extensions on VSCode couldn't understand if the imports where actually used in the docblock annotations. Well, they couldn't undestand most of what was going on docblock annotations to be fair.
Things like "organize imports" and "rename symbol" were missing too.
They are different issues: Windows and Mac OS users using 21:9 monitors will have aspect ratio / black bars problems, Linux users with standard 16:9, 16:10 monitors will have problems with full hd and 4k resolutions.
And even if these are two small user bases please consider the efforts required in order to fix the problems we are talking about. What could possibly take to lift the block on full hd as I am already doing with some browser extension? How hard could it be to copy the crop detection algorithm from mpc?
I own subscriptions for both Netflix and Prime Video and (try to) use them most of the times from my Linux desktop on a 21:9 monitor. I have to force proper full hd resolution using a browser extension but can't find a way to fix aspect ratio / black bars problems. Just yesterday I tried to watch the third season of Stranger Things and I had black bars on all the 4 sides. After boring my SO for about 10 minutes messing around with extensions I just fired up qBittorrent and fixed the problem in 2 seconds using the autocrop feature in mpc.
I end up the torrent way so often that I'm starting to doubt the reasons that push me to support these platforms and their broken features.
Is the desktop userbase a niche so small they can afford to ignore?
I often see comments about this product piggybacking on other things' visibility here on HN.
It is closed source too.
Can you please put your ads somewhere else?
Using nestjs/typeorm/type-graphql for my current project. I have to admit it is quite refreshing after all of the yaml and docblock annotations of the Symfony/Doctrine/APIPlatform ecosystem.
> The only thing you should skip in both frameworks are 'annotations'. But this is easy to do.
If you are using Doctrine the only alternative to docblock annotations is XML because they are deprecating YAML support.
I really hope they build support in the language itself. I can't understand their fierce opposition to a feature every other major object oriented language has. They are only forcing a large part of the ecosystem, everything that is Symfony or Doctrine based, to use the horrible docblock work around.
After quantum I did my best to switch but I had the following problems: no scrollbar search highlights, terrible Linux/gnome dark theme integration, angular source maps not working. After a couple of weeks I got back to Chrome.
> Angular is dead? Most don't even want to touch it again ( Great ).
I don't get the Angular hate. I work with it daily and seems like a productive environment. I did some tests with React and Vue too and couldn't find any relevant advantage. Angular has batteries included tools for a lot of tasks: i18n, routing, isomorphic builds, web components, etc.. You get a cross platform mobile development environment too using NativeScript and a somewhat Angular-esque backend development framework using Nest.js. Seems like a good deal to me.