What developers _should_ be doing is disabling such animations if `prefer-reduced-motion` is set in your browser. This way, both people who have trouble seeing stuff when there's too many complex color animations as well as people who "just don't want to deal with all that mess" can specify what they want to see, and the code can change based on their preferences.
Unfortunately, I believe for "custom jobs" like this you'd need to explicitly state that you don't want it to occur because it won't happen by default, unlike some other stuff that's more standard in the browser.
Finale was my first notation program, and while I switched to Sibelius out of necessity during college, I never really liked it. Will definitely check out Dorico, heard good things!
Is anyone else sick of the "European Parliament" deciding the rules for the rest of the Internet? I know I sound like a dumbass American here, but I feel like there's gotta be a way for the EU to get what they want without bothering everyone else in the world constantly...
The issue is that they keep enacting laws that have good intentions, but are written poorly and without any sort of experience in the technical realm. This results in the laws' implementation being filled with weird loopholes that you can use to get around the extra work while still maintaining the legality, but completely missing the intention of the law in the first place. It just seems like a massive waste of time to me.
Is anyone else sick of the US deciding the rules for the rest of the Internet? I'm fed up of American advertiser-friendly doctrine deciding what is acceptable content anywhere in the world.
(joking, but this is kind of an unsolveable problem of having a global network without a global governance system, you're going to run into mismatches)
Basically, you are ok with only the US influencing the rest of the world?
Because the US has control of the DNS root zones, is powerful enough to create a chip ban on China and has back doors in half the planet's machines through programs like PRISM or systems like IME. I think from an influence point of view, they are quite powerful enough.
Given the US also went to war with Irak despite the entire UN voting against it and while lying about WMD, have a mass spy program on their population, and will soon reelect a convicted felon, it's a good balance to have other parts of the world trying to have a say as well.
The human world is full of imperfections, but we usually average it at scale.
I'm not really sure what you mean, changing the timezone of a country is certainly their prerogative and "technical experience" doesn't really have anything to do with it.
The EU is one example here but many other countries have timezone/DST changes, the EU is one of the places that don't change timezones often. The US on the other hand has such variety in timezones and DST observance, not even following state borders, that it's a real pain to support.
That has nothing to do with the European Parliament. Or not in the general case. If you're interested, dig yourself into the changelog of tzdata. Timezones are inherently political.
Ugh...the tax shit in the US is so annoying. At least your e-commerce system is meant for a single kind of transaction, I worked on a more multi-purpose system (that was also open-sourced! https://github.com/workarea-commerce/workarea) that handled everything from physical items to buy online pickup in store to digital items to subscriptions. It was a LOT of work getting that tax system in order! We usually recommended our clients work with a company like Avalara or TaxJar (which is now just Stripe) so they wouldn't need to take on the burden of taxes, but a lot of folks didn't and just used our stuff. It got confusing lol...
While I'm aiming at just one market. The tax system supports having multiple. You can define products as physical or not. Define which tax type it is and then define the tax rules per country for that tax rule.
I'm going to be adding integrations with tax jar to help make it easier for keeping tax rules up to date. Do a daily/weekly check for tax in each area and then save it.
> The team has a history of over promising and underdelivering (or scamming - depending on your perspective).
Their attitude of not communicating anything and basically inventing stuff the R1 can do without actually having the engineering to back it up is what is "scamming" to me. Over-promising and under-delivering is one thing, but lying about what something can do and then going back to the engineering team to "just make it happen" is what I am reading between the lines here.
This is awesome for folks who don't use their own custom status bar! Personally, I use SketchyBar and Yabai for window management. SketchyBar is shown almost all the time, but the status bar is set to hide unless I have my cursor at the top of my monitor. I like this because it's a good combo of having my "status bar items" all compacted on the right, with the useful information I want on the status bar at all times...such as battery level, current weather, volume, the date/time, as well as the focused window.
For those who don't want to install a custom status bar, this seems like it would solve similar problems of the status bar getting way too big with all these programs running in the background.
After years of watching spyware make a ton of money on their platform, Microsoft took a page out of Apple's book and created their own spyware for Windows.
As someone who used Go since before v1, I can say that Go's approach to dependency management was basically "we don't want to touch it until we know we have the right idea". At the time, dependency management solutions were pretty primitive to what we have today...there was no caching, and if the central server where you got your dependencies was down, you were shit out of luck. So this was really not a bad decision for the language maintainers if they wanted to keep their sanity and not subject their user base to "legacy on arrival" software. By depending on URLs and using a `$GOPATH`, this problem was solved from a localized perspective...as a developer, I could vendor in packages, not check them into Git, and compile the program. It worked.
However, the biggest problem with depending on packages in Go back then was that it was difficult to communicate to other people on your project the exact version of the dependency that you wanted them to install. For projects in which you were the only developer, this wasn't an issue...but as soon as you started to use Go in a team setting, it became a real blocker toward getting your work done. Go developers needed _some_ way to communicate what version of each package they wanted to install, and a bunch of solutions popped up to help with that. But they were all still bound by the `$GOPATH` constraint and such.
Although it took a lot longer than many predicted, I'm still pretty happy with how Go approached dependency management at the end of the day. Generally, all I have to do is import a dependency from a known URL and my editor/Go modules will take care of the installation work. This is way better than the JS world, in which if I want to just sketch something out I have to actually install the dependencies I need otherwise TypeScript will yell at me. With Go, it all seems to happen automatically.
Unfortunately, I believe for "custom jobs" like this you'd need to explicitly state that you don't want it to occur because it won't happen by default, unlike some other stuff that's more standard in the browser.