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

I do. Why not?


Not water proof and definitely big for its capacity.


Yes, hence why I'm sure companies with 100x the budget can do better.



Ah, I must be living under a rock, thanks :)


On Pixels too.


Pixel 8 is nearly 3 years old. Battery is still perfectly fine.


My Pixel 4a would also still be fine. If Google had not killed the battery. I think by now Google has asked (=paid) people to swap batteries on at least 3 different Pixel phones.


You absolutely do need SDL, it's full of knowledge by humans from trial and error over years of using input devices in the real world.


Good point. I think it would be fixable by using the Change Time instead of the Modify Time, because that changes when moving the copy over the original.


Good news, I've been working an adding file content hashing to Ninja: https://github.com/ninja-build/ninja/pull/2735

That will fix the "switch branches back and forward" case :)


Audio APIs on Android are completely different than on GNU/Linux.

3D was also different (OpenGL ES vs OpenGL mess), only now it's starting to become kinda the same with Vulkan.


Nope, they are also available as they are Khronos standards for audio, and Mesa also does OpenGL ES.

Do you need a tutorial?


You mean OpenSL ES? Is anyone actually using that on desktop? On Android there's https://github.com/google/oboe.

While Mesa has OpenGL ES it wasn't always available (for example not all drivers are using Mesa).


Well if it's GPL without CLA and they accept outside contributions, they can't relicense / make it propriatary. Unlike with MIT.


Step 1: discontinue the public repository, step 2: sell access to your GPL codebase.

The GPL (and even the AGPL) doesn't require you to make your modified source code publicly available (Debian explicitly considers licenses with this requirement non-free). The GPL only states you need to provide your customers with source code.


Sure, but it also allows your customers to modify the source code you provided, and distribute/sell it. With MIT they can simply relicence it and sell binary-only versions. The open-ness stops at that point.


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

Search: