PyErr_SetString

I think this is an important point.

The first priority needs to be to make it easy and obvious to do the right thing.

Trying to make rules to forbid doing something insecure isn't helpful at all. If I need to do something and the only way I know how is the unsafe way, there's a big risk I'll pick that way. Unfortunately, it seems that security work is often just about trying to stop people from doing things, not helping them to do it the right way.

While I think this looks really cool, there are people who think domes are not the way to go. Part of the reasoning kind of makes sense.

https://caseyhandmer.wordpress.com/2019/11/28/domes-are-very...

Either way, these things are fun to read about...

Does anyone rememner the Jolla phone?

I had one and it was great! The reason: You could do a lot of the necessary things with a phone, like:

* Making calls

* Sending text messages

* Set an alarm/timer

* Take a photo

You could also do a lot of the less necessary things like:

* surfing/facebook/reddit, through the web browser.

* playing (some) games

But, those less necessary things were just a _little_ too much effort to be worth it. Surfing was a bit cumbersome and I didn't have that many apps on it.

I found myself using the phone less for unnecessary things and just as a tool to actually do things I needed. I loved it for that. If they sold decent phones still, I might probably buy another. Now I'm back to android and use the phone for more unneccessary things again.

Also, I liked the sounds and themes on the Jolla.

Swedish church membership means an additional 1% tax on average.

"The "1 month of battery life" is such bullshit"

Yeah, I'm going to go ahead and call BS on that too. Here's the info about standby time you can find for iPhone6:" "Up to 16 days (384 hours)"

I'm interested in knowing if anyone even got half of that. And if you actually start using your phone it'd go down a lot more (which you probably would want to, since you know... you bought it to have as a phone)

"If you think about it, Android's problems with open source allowing manufacturers to have their own flavours of Android..."

One is not really dependent on the other. You could use open source and not allow modifications or you could use closed source software and allow endless customization.

I also don't consider it an "android problem" that manufacturers do this. Most of the good stuff ends up in standard android after a while, which wouldn't have happened if no one was allowed to make the changes in the first place.

Yeah, that could explain it. Sort of like how you rarely see Java client applications...

"I think its simple. Unless the person is interested in Mono they don't develop for it and don't have any interest in supporting it."

But why wouldn't someone who IS interested in running the application on Linux simply do the last bits to get it to other platforms? I have NEVER seen that happen.

"And while there are thousand of useful C# programs I doubt many don't have direct python / Linux competitors readily available that do near enough the same thing."

Sure, but I refuse to believe all the competitors are always doing a better job. There should be at least some application that found their way over to for example Linux.

"I know it is cross platform, but the focus of the eco-system in very much on Windows."

There's a funny thing about its cross-platform nature: You almost never see C# apps on other platforms. Why is that? There must be thousands of useful C#/.Net applications made that other platforms could benefit from, but the ONLY ones I've seen are the ones that targeted Mono to begin with. Nothing else.

Something fishy is going on here.

If I'm not mistaking, ARMv7 supports PAE, which will allow you over 4 GB of memory. Perhaps not all in the same process, but still...

"What I find issue with is that people will completely dislike a solution for the brand alone. I've seen this for years when I've suggested/supported Mono in Linux."

To be fair, Mono never delivered on its promises. There must be tonnes of .Net applications that Linux users would have been thrilled to get on their platform. Yet the only ones I have seen running on Mono were the ones that were specifically targeting Mono, not ones that were running on windows and just happened to find their way to Linux.

So, either most .Net applications are crap that no one really cares about or they were tied to the windows platform. Of course, it could just be blind, unmotivated hatred, but that's not how I've perceived it.

I don't think anyone is arguing that if Microsoft blinked out of existence, no one would be inconvenienced. What a lot of people ARE saying is that "if not Microsoft, someone else."

If Microsoft never bought the software that eventually turned out to be Office, someone else would have provided a solution. If Microsoft hadn't bought (and resold) QDOS, someone else would have provided an operating system for IBM, and people who make chairs wouldn't have seen a big difference today.

Of course you can. But is it always an equal share of bad code for each language? If not, then you have to admit that the language itself will encourage or discourage bad code or bad coders.

Come on, you have to give me something to argue with. I can't just sit here agreeing with people. :) Yes, Visual Studio outside the MS sphere is not the greatest. C++, C#, VB.Net, F# - fine. Does anyone use it for anything else?

Then again, most programmers today aren't C programmers. And developing in Java/C# really makes a good IDE mandatory.

The point is valid, even if you have a point in what you write too.

"I want to be that go-to person, that expert, that guy who Gets Shit Done."

I have a few bad experiences with "the guy who gets things done".

There's an old saying that the last 10% of the work takes 90% of the time.

If you stop after the first 90% (or why not at 80%?) and jump to the next exciting project, you will be percieved as very productive. And because you don't put in the time to properly document things, you'll be the only one who knows it all and you'll be percieved to be a guru who knows everything.

Sure, it might not work perfectly, but it's only minor flaws that someone else can fix. Right? You're too busy being productive in your new project, leaving a mess for people to maintain in there.

And it works. Your managers see you as the go-to guy. You will get things done. And the fact that people then spend ages of time to patch your work just proves how much more efficient and better than them you are.

Yeah, you probably guessed it: I spent the day yesterday cleaning up someone elses unmaintainable, undocumented mess. Someone who is now working on a new project.

I agree with what you wrote mostly. What dropbox could do to mess up and give Google a chance to do something much better is this: don't give people more free space when the average user struggles with the 2GB limit. One of the things that made gmail a success was that hotmail and the rest cheaper out on space. People had to constantly clean up their 2MB mailboxes. Google might be able to do the same again if dropbox don't offer more space for free. But that would take away from their earnings, so it isn't an easy problem to solve.

I am aware of that :) When developing OS it might make sense to have two machines. (unless you can run in a VM, which I think many could)

But, not everyone at MS works with windows, which is why I was a little surprised about the statement that everyone had more than one machine.

Yeah, I thought that sounded strange. It would even be slightly embarrassing if all people needed more than one machine to get their job done.

"All employees at MSFT get more than one machine connected to many screens"

Just out of curiosity, why does everyone need more than one machine?

Have you seen any actual numbers on this? I've googled around a bit and can't seem to find any.