16,803 karma · joined May 21, 2012
Phone + not being an english native speaker can result in serious comment injury.
It's just that people carry on. They don't build their life. They don't make conscious choices, orientate their actions or try to think about the society they live it.
They just go through it, going from one small short term objective to another, most of the time motivated by a small pleasure or to avoid pain.
That is why people get fat, get stuck in traffic going to a job they don't like, going back to TV eating unhealthy food and indulging some kind of addiction.
Believe it or not this is also a big cause of couples staying together, marrying, making children. Not the grand idea of love. Inertia. Status quo.
I haven't seen panic. People can't stop listening since they haven't even started. Most people don't know about this, don't care, or can't see the big picture.
But repeating works.
We know it works, because that's how TV ads work.
So I'm all OK with repeating that again, and again.
People getting tired of it ? Meh, they still watch TV after the 1876th coca cola ad. And then they go buy soda.
I'll take the chance of repeating a wholesome message.
- solve a new problem
- solve an existing problem better
- solve an existing problem cheaper
A new tech MAY allow that, and it MAY be used successfully toward that objective, but even in that case, that's hardly the core of it for most cases. Not saying it does not happen, but there are much more at play.
Yeah but writing the code is not what's expensive on this project.
Hot weather and good infrastructures so you can live in the street.
Liberal so you are not bashed out by the cops.
Rich so you can beg for money.
Many water points.
Strength in number.
I'd add:
- kde-connect. It's awesome to be able to control my computer for my phone, especially while watching a movie.
- alternative stores. Being able to use aptoid and f-droid let me use the full potential of the phone without tying it to an email account.
- productivity concepts arrive first on android. We had wifi hot spot. Quick wifi/bt/3G switch first. Etc. With apple, you only have what Apple though about, or could copy later. With Android, the community can implement many things.
- USB-C charger. I don't want yet another charger/adapter
- my phone will still work in 5 years. No "oh the home button is broken" scandal.
In the end, I only keep airdroid for sharing files and contacts.
No thanks
- the time of the day you eat it (you will more likely store things if you eat it late than early in the morning due to your homonal cycle)
- the duration on which you eat it (the infamous 9 hours popularized by dr rhonda patrick)
- what you mix. Eating the same amount of calories in pure fat, or in a mix of 50% fat and sugar will not result in the same process by the liver.
- insulin sensibility. Which is influence by the quality of your food. E.G: how much sugar it contains.
- ability to process said food, again influenced by the state of irritation of your intestine and your microbiome, and hence influenced by the quality of your food. E.G: adult can get irritated intestines by intaking dairy product after they lost their childhood ability to proess it as well.
I know it's a convenient shortcut to say "calories in, calories out", especially since it's easy to demonstrate (the anecdotal Twinkie diet made us all think). But if we keep repeating that, we are not helping people to lose weight. Dieting has a very low success rate because of the solely focus on the calorie count, while using the informations above as well lead to less rebound and frustration in my experience.
> + Static linking
It's actually what I like in this project. Dynamic linking causes many issues, especially on Linux, where you never have quite the same libs depending of the distro. If I want a standalone exe, I want static linking. If I want dynamic linking, I'll make a deb or a rpm.
> + No extension (shared library) support
> + The module importers look over-engineered / too complicated
Man, the project just came out, give it time. You're very harsh on this.
> + Custom Python distributions
Well, yes. That's why it works. Otherwise you are back to require a C compiler on the machine or use dynamic linking.
> + Not sure what Rust gets you here, besides additional complexity
- link to the custom python distrib, allowing you to use the nice rust toolchain instead of the mess that is the c toolchain or dynamic linking
- free rust / python interrop. This is very interesting.
- potentially cross compilation and even make the tools stand alone itself
> + No support for Python 2.7 (Python 3 drops support for Windows XP which is still a legit platform for many scenarios)
Python 2.7 is reaching EOL in a few months. It's perfectly reasonable to not support it. No poney.
"yeah, we take back your transplanted heart but don't worry we will give a refund so it's not immoral"
E.G: in Python 3, it's recommend to use str.casefold() instead of str.lower() for this:
>>> "Straße".upper().lower()
'strasse'
>>> "Straße".lower()
'straße'
>>> "Straße".casefold()
'strasse'
>>>
Depending of the context, a little str.strip() and/or a str.split() + str.join() may also help. User usually don't want to consider blanks when entering data (e.g: an address), while it's important for machines (e.g: a password).Now like @lmm said, this only normalize the codepoints. Meaning is of course, impossible to be sure that way.
What's your metric to say that ? After all, it's a system language, not a web one or scripting one, so it's not likely to go to the top trending stats very fast. Not to mention we had a stable version for only 4 years.
Fatigue and speed of execution seem central.
Nuitka worked immediatly, but still dynamamically links libc and doesn't allow this nice rust/python interraction nor the possibility of future cross compilation.
PyOxider packages and accesses the python files I think, so they are here and available.
PyOxidizer offers a solution that:
- works on Windows
- can produce executable for Windows, Mac and Linux, but also potentially cross compile from any of those in the future
- results in a stand alone executable, not some filesystem abstraction
- as such, the target machine doesn't need to have anything installed
- it also offers to embed Python into Rust projects, and Rust into Python projects
A better alternative would be the excellent nuitka (nuitka.net):
- it compiles Python to C
- it's very compatible, very reliable (I battle tested it)
- works better than the alternatives like py2exe, cx_freeze, etc
- does provide a standalone executable
- more mature that both of these projects
But:
- no cross compilation
- no rust / python interoperability
- more complicated to get working on windows
So I'm really excited for PyOxidizer. It may make the task of providing a stand alone executable even easier than with nuitka, and as a bonus, may build a bridge between the Python and Rust community, which really are meant to play together.