Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

Swift is already way more popular than dart though.

But Swift doesn't run on Android, does it?


It does. It has been able to for some time now. A team I’ve worked with used it to build a cross-platform library. Swift wasn’t the first choice but the short story was they didn’t choose C++ because they didn’t want to hire C++ devs to maintain it.


If that library is open source I'd love to take a look at it.


Did the team look at Kotlin? Seems like Kotlin Native on iOS is a more viable alternative than Swift on Android right now for cross-platform development.


And yet there are people complaining it's too slow, or too fast.

I don't think there is any pace of language evolution that will never be criticized.


Rust has been really great at incremental language upgrades because of clippy. Stuff get deprecated, clippy issues warnings, buy the time support is dropped your code has been patched.

It feels like we are in some new weird software engineering world where the code is only alive while its actively maintained and worked on. The libraries that are shipped in the OS seem as constant and fixed in time as x86, basically completely abstracted by the constantly evolving software on top of it.


Compose, rarely. Read and edit with plain text editor, it's common.


I did it like three times already today.


What editor did you use?


vim / sublime text, depending on context.

I do a lot of troubleshooting using CLI tools like grep and wc.


A single source of trust for the dependancy transport.


How did you deal with C-extensions, since apparently most don't support it at all (which is a shame, apparently we messed up culturally here).


I didn't :)


There are plenty of things that could have been down, but the Python core dev team is small and very resource limited.



Read the other comments and people says it moves too fast.

People are never happy.


And beazley wouldn't care, right?


Spwaning the process is not the only problem, communicating between them is also expensive.


async / await is just a protocol to delegate async behavior outside of your control flow.

You can provide the async behavior using any solution you want: threads, io event loop, subinterpretters, subprocess...

It can all be called from async / await.

In fact, if you use asyncio, the lib, it provides mechanisme to await from threads, subprocess.Popen, and multiprocessing pools.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: