Re: i have an idea for an app
China does this in their country to ALL foriegn apps. The US position is (still) a lot more friendly to Chinese apps than the Chinese government is to foreign apps.
340 posts • joined 10 Mar 2018
I've worked on a lot of Dell Laptops. They're always designed to be repairable. I think the reason is that Dell sells a lot of repair contacts to companies and then has to repair their own laptops. It makes sense to build a repairable laptop to reduce cost of repairs if you're the one paying for the repairs.
The "paper" referenced suffers from a really small sample size. For the public test they had 26 participants, only 6 of which were women. For the private, there were only 24, with only 4 women.
You're drawing conclusions based on sets of 4 and 6 participants. And all I had to do was scan the pdf for a few minutes to find that out. Why report on things if you're not going to assess the source?
PHP and .NET address different market segments. If you just want to get it out the door quickly PHP is faster, but .NET is more structured. I'd use PHP for smaller applications and .NET for larger ones. There is a big difference in design philosophies between PHP's scripting language design and .NET's JIT-compiled nature. PHP is never going to perform as well for larger more highly-threaded sites, but it's a good choice for things that would take much longer to write in .NET. Some other platforms bridge the difference like node JS. It's about picking a good tool for the job you're doing.
As for versitility? .NET is probably better for that because you can call native code and there is a more advanced threading model. But complexity comes at a cost, mostly a time cost.
My current cat has a tendency to chew wires, because he seems to think they're string. He bit through a Logitech G500 cord, which I had to replace at great expense while the replacment cable was shipped on a slow boat from China. I coated the cables with laundry soap which has henceforth put him off chewing my computer wires.
Our current IT manager is so incompetent that for anything even remotely difficult, he just bothers me until I do it. I'm a software architect, it is on no way my job to do any IT at all and I also theoretically outrank the guy. But it's a small company so if I don't do it, it doesn't get done.
I'm just waiting for him to majorly screw something else up like he does every month or two and have it tweak the nose of the CEO (many have been fired for less).
I'm with you. I, have a desk, Herman-Miller office chair, 2 4K monitors and a desktop more powerful than the one in the office. Our juniors mostly have much worse setups. Generally a laptop of dubious quality on a table or coffee table. I feel bad about it, but I'm sure they're more anxious to get back to the office than I am. Not to mention then people who have kids, that's a whole other problem.
Apple places huge restrictions on iOS apps. If only they'd asked one competent iOS developer about this at the beginning. The first thing out of every iOS dev's mouth in my experience is "Apple won't let you do that, but we can do...". iOS development is a pain, and if Apple didn't have the market share they currently have, no one would be writing iOS apps at all.
No it doesn't, those are two different points.
1. OP was surprised that a technoglogy that is very popular exists
I hate it when people who don't know anything about a topic run off on things they don't understand.
P.S. None of your "attacks" can target client-side frameworks, that's ridiculous because all of that code runs client-side.
I think VR headsets make everyone sick eventually, but people have varying tolerances. I can generally stand about 2 hours, sometimes up to 3. But some of my friends get sick in minutes. That said, I'm not sure how much I actually enjoy VR, the inconvenience is pretty high and while it can be very engrossing I don't find myself pulling on the headset that often.
This is great news for the 3 people developing apps on ARM64 Windows who'd want to use VS Code...
I'm still not sold on Windows on ARM64 because the hardware makers don't seem sold on it. The only readily available ARM64 Windows system is the Surface X and Microsoft has proven many times that they're unable to kickstart new architecture support in Windows by building their own hardware. I'd love to be wrong here, but 3rd party ARM software on Windows is basically non-existant.
A sandbox handles it in a way that all users can understand. Having to set permissions like that is very complex and requires a bunch of setup. It also doesn't restrict things like network access, camera acess, and mic access by app.
Per-app sandboxing would greatly improve the security on Windows and current legacy permissions are not a substitute.
What a mess. It would be nice to have sandboxed apps in Windows but Microsoft keeps confusing the matter over and over. Secondly they're not providing useful guidance for porting existing apps to their new UI either. I'm so glad I work with web apps, because while UI in web apps has it's issues, Microsoft seems dedicated to making UI on Windows the most confusing thing possible.
Additionally, and this may come as a shock to you. Good developers can pick up new languages and frameworks pretty easily. It's not like those crusty old IT guys who freak out every time a Windows patch comes out.
And this endeavour is doomed... I mean it was already doomed because their business model was flawed, but now they've pissed off all their customers AND their new business model is still flawed (the majority of people .don't want to pay monthly for the limited utility IoT devices for the home provide).
Ahh, System.Reflection, that namespace is the sort of thing you have to avoid if you care even slightly about performance. Too many times I've had to shoot down a junior dev who has come up with some novel whiz-bang code that relies entirely on reflection. Sure you might save on some code and not have to write those interfaces I asked you to. But it'll perform like crap.
Stored procedures really lock you into a specific database layer and can become difficult to manage in larger systems. So yeah, that can make sense, but it can create a lot of problems, you have to be careful when you split up your program logic between the DB and model code. We have an older web app at work where ALL of the logic is written in stored procedures, including things that make no sense to have in stored procedures (like ones that literally run .NET code, why is that even a thing?).
VB.NET VS C# should perform basically the same because they run on the same runtime. The main reason you'd not want to use VB.NET these days is lack of popularity (good luck hiring a team with a lot of VB.NET experience) and it's relative lack of language features (not a huge loss in my opinion.) .NET Core doesn't support it yet either, but apparently that's comeing eventually after .NET 5.
And as for... C# queries.... I think you probably mean Entity Framework, that's just an ORM, nothing to do with C# and ORMs all have the same problems. You're trading development speed for performance. So obviously you end up with better performance if you write direct to your database.
Hmm, all I did was throw out my HP printer and buy a Canon Megatank printer. No way to lock down to only Canon ink cartidges... because it doesn't use ink cartridges you just squirt the ink in the top. And admittedly, the Canon ink is pretty cheap and I havn't had to actually buy any because the full set of ink that came with the printer (HP would never do that either) has lasted for ages.
Biting the hand that feeds IT © 1998–2020