151–160 of 269 posts
Earlier quoted context omitted.
> If your excuse is editing MS Office files, LibreOffice supports the formats and works For very small values of "works". I've found that even high school projects turn out to be a bit too much for libre office.
Interesting, I found the opposite. My MS office doesn't even have 'export to PDF' and Libre has it.
Earlier quoted context omitted.
Interesting, I found the opposite. My MS office doesn't even have 'export to PDF' and Libre has it.
Sounds like you're comparing a 10 year old Office version to a current LibreOffice version.
Maybe that's why Microsoft is pushing hard to move everybody to an online office subscription?
Earlier quoted context omitted.
> The other solution is to rebuild infrastructure on top of a different platform but that's prohibitively expensive. I really don't have a lot of sympathy for companies that lock themselves in to a proprietary platform.
Do you at least pay those that give you the free one?
Earlier quoted context omitted.
Shoddy or realistic? I'd hope more security researchers work with systems that aren't perfectly configured because they won't be in the real world.
There's a difference between "testing things on a reasonable reproduction of real-world systems" and "claiming Windows doesn't work correctly because you don't read the documentation."
Sensible defaults matter.
The switch to Linux or other free operating systems is long overdue. If your excuse is hardware support, then (1) your hardware is probably supported these days and (2) you should not buy hardware that is incompatible with the operating system you plan to use. If your excuse is editing MS Office files, LibreOffice supports the formats and works great, and MS Office on Wine is an option. If your excuse is games, then…
> If your excuse is editing MS Office files, LibreOffice supports the formats and works For very small values of "works". I've found that even high school projects turn out to be a bit too much for libre office.
Excel teach bad habit about having list every where not maintained.
I run Windows in a Parallels VM on my Mac. This VM needs to, on occasion, connect to the Internet. Any way I can--from the outside, without needing to trust Windows--be forced to whitelist what the VM is and isn't allowed connect to?
outside /etc/hosts redirect to 0.0.0.0 inside (c:\Windows\System32\Drivers\etc\hosts) assuming it is being respected, but how to find list? is very difficult I think, as can change by Redmond c&c server at no notice,
Earlier quoted context omitted.
Its depressingly popular in the US for small & mid-size retailers and businesses. NCR, Loc, IT Retail, et all are built for Windows, and in the pharmacy arena you've got major companies like CVS using stuff from companies like Integra (not the telecom company, the pharmacy one) that thinks moving to SQL Server 2008 and C# with a full rewrite is the route to go for their major PCI compliant products. It confounds me t…
In all fairness, writing in C# and targeting SQL Server is not locking you into Windows unless you use WPF or other Windows specific parts of the framework.
Sure, you can technically run C# on a Linux box (eg: Debian), but the last few times I had to (to interface with some point of sale hardware) I literally ended up just rewriting the driver in python. No desire to maintain something so foreign to the rest of the codebase when python can handle serial devices just fine.
Wrt not using a database connector, just why? Your literally locking yourself to the SQL Server licensing model, which blows up when you allow BYOD on every android phone, and they're all connecting back to your SQL server. Postgres and MariaDB meanwhile have no issues. Let alone if you hit the 10GB DB size cap, or need more than 1 cpu core or 1GB of ram to cache your database.
Earlier quoted context omitted.
I went through the same thing last year. I spent two months trying to plug all the holes in the enterprise version, for a medium sized healthcare client, and eventually gave up. The LTSB edition looks promising but I haven't put it under the microscope yet.
LTSB (aka: long-term servicing branch) I'm not sure if it's comedic or tragic that the version so very many users would want most, is not only the version with the worst name, but also the version Microsoft discourages people from adopting. Critical patch support, infrequent updates, and excludes crufty bloatware. What's not to like?