In reality, there are 2 kinds of orientations: bisexual, and closet bisexual.
764 karma · joined October 4, 2020
In reality, there are 2 kinds of orientations: bisexual, and closet bisexual.
I've done cocaine, marijuana, mdma, speed, xtc pills, and some research chemicals. Protips: don't smoke, and never combine any two drugs. If you really want a certain substance, do at least the first session with someone sober to keep an eye on you. Never accept drugs from strangers and don't give in to peer pressure (which can be pretty tough at times when self-confidence is lacking).
I am disappoint.
I first used KDE over 20 years ago, version 2.x. KDE 4 was awful, and I moved to Gnome. Since version 5 I'm back on KDE and most notably, the battery life of my laptop is twice as much! And it's configurable. And beautiful.
But if they want my money, they'll have to stop filing silly DMCA requests and open up the source at some point in the future (like ID did).
It really is amazing. The best trick in Writer is to use the "Styles" sidebar and apply document-wide styles to the document like you would in CSS. This makes layout in large documents a breeze.
If you don't like the UI, there's "View > User Interface..." where you get to choose between 7 different UI layouts.
You know I moved from Netscape 3.0 Gold to later versions, to Mozilla, to Phoenix, Firebird, and then Firefox. I tried other browsers but it's always a subpar experience for me. My only gripe is that they kept changing the UI.
dpkg-statoverride --update --add root root 0755 /usr/bin/pkexecAlso, I'd prefer a language with slow incremental changes because it eases the maintenance burden.
Also I like to play old stuff from modarchive.org in milkytracker like NOFACE.S3M
TFA music didn't play for me in FF95 on Linux unfortunately, just chirps.
(And a copy of the ECMAScript specification.)
GNU+Linux worked just fine back then, and it still does now. KDE was already a thing. To start with computers, I'd recommend the GNU Manifesto. Free software is important. These days, anyone using a computer without a FLOSS operating system on it is just ignorant. There's been TV ads. CDs by mail were free. There are magazines. Arch has a wiki.
And to those who are willing to make their computer work for them again: welcome to the FLOSS community. Hope you enjoy it!
My advice to you would be: defense in depth. Get yourself a good firewall (e.g. pf). Follow security best practices. Be diligent. Keep separate computers for separate tasks. Omit binary blobs as much as possible.
You can practically consider yourself already owned these days.
Responsive images are kind of funny in the sense that my webpages are nearly twice the size on mobile vs my laptop. The screen may be smaller, but the CSS pixel ratio is 1 on my laptop vs 3 on an iPhone.
> Mozilla need to [...] build a new browser
See The Book of Mozilla, chapter 11. >and a “browser toolkit” to let other people build their own
XULRunner was essentially this.To me, having reset styles feels like using unwanted globals in a programming language. Styles on html and body are ok though, as there's only 1 of them on a page.
* A hydrator/extractor that changes the type of the value it handles
* A task or job that has a certain priority to it
If you mean classes with private constructors, those are technically illegal. According to the PHP manual, constructors must be declared public. The fact that private constructors work at all should be considered an implementation detail.
Breakage occurs when something is said to be a class, yet isn't a class but still appears in the parameter list of a constructor. The container would instantiate a ReflectionClass of whatever is being requested and pass that around. At some point it'll call newInstanceArgs either with configuration-provided arguments or with auto-wired dependencies. The first case could still work, but foregoes auto-wiring.
Because it's not possible to instantiate an enum, if one appears in the constructor of a class it'll break auto-wiring. I've written my own IoC containers and one fundamental assumption in them is that when class_exists returns true, it is what it says on the tin. Using a specialized factory would still be possible. I wonder if other containers would break on seeing enums as well, but I hope they fixed this because it's not mentioned in the breaking changes. The documentation for class_exists doesn't mention enum.
Static return type, useful but since I use interfaces for everything it's not really needed. Union types, also not really needed because either 2 interfaces share a common ancestor or I'll have separate methods for different types. But most of the time, I encapsulate things behind interfaces that do one thing, so having different methods per type can often be avoided.
Named arguments are a pain for me since now I can't change parameter names anymore. This is particularly annoying with different coding styles in dependencies vs my own code. My code ends up not conforming to the coding standard that I've used since it was introduced (PSR-2R).
Exceptions as expressions is a nice to have, but exceptions in general are a thing to avoid doing. Not that things can't go wrong, not that chugging along in the face of errors is good, of course it's not. But if you have a lot of exceptions in your code, that's a smell of bad design. I've got 13 different exceptions used 20 times in total, over 4683 LoC on my current project. Mostly, whenever one of them is triggered, whatever I changed last was incomplete and led to an inconsistent configuration.
That said, your use case for PHP is probably very different. Especially since I don't care much at all about performance anymore. I used to, but CPUs are so much faster nowadays and PHP itself has improved.