195 karma · joined August 31, 2013
3,3′-Diindolylmethane (DIM) decreased the Streptococcus mutans biofilm, a leading contributor to plaque and cavities, by 90%.
Source: https://scitechdaily.com/90-reduction-scientists-discover-na...
Open Source LLMs Not Exempt:
Open source foundational models are not exempt from the act. The programmers and distributors of the software have legal liability. For other forms of open source AI software, liability shifts to the group employing the software or bringing it to market.
Source: https://technomancers.ai/eu-ai-act-to-target-us-open-source-...
https://techcrunch.com/2021/04/07/twitter-said-to-have-held-...
The hard truth is software can't be patented and Twitter could copy the concept verbatim without paying them a penny.
1. Name five pop songs made by german artists.
2. Write a PHP function that replaces newlines with dots in a file.
3. Name the movie about a bowler whose identity is mistaken.
https://www.dutchnews.nl/news/2021/11/japanese-leaf-flea-may...
Might want to look into what the H of HN stands for.
Nader Dabit has done an excellent job describing the use cases: https://www.freecodecamp.org/news/what-is-web3/
Your kid enters a wrong birthdate on YouTube? Gmail account gone. File identified as DMCA material uploaded to Gdrive? Gmail account gone. Theorized about covid origin? Disinformation; Twitter account gone.
See the pattern? The key to a decentralized web is federated, decentralized identities. Sure, you can self-host videos, blogs and forums and let people create accounts for every website, but being able to log in with your wallet and pull graph data is THE non-financial killer app of Web 3.0. Log in with Metamask or Phantom on a few sites and you'll see what I am talking about.
- It's multi-framework (Vue, Angular, React or Svelte); easy to pick up for web devs
- The per-framework implementations are fairly similar to the web-variants (except it uses NS component tags vs HTML tags)
- UI abstraction layer that maps the NS components to real native UI components for iOS/Android (instead of Flutter's gimmicky pixel-by-pixel OS element duplication ala Adobe Flex)
- Use of native UI elements lead to performant UI elements (recyclerviews, tabs etc). React Native plugin devs had to tediously re-create elements like the recyclerview with custom logic (see 'RecyclerListView'). The core team adds new UI elements fairly quickly after OS releases, as they only have to create the bridging code
- Out-of-the-box code bridging; access native methods/variables on iOS/Android from JS. E.g. accessing the Android notch API can be done with a few lines of JS
- Recognizable CSS elements for styling (margin, borders, gradients, box-shadow)
- Performant; fairly quick cold-boot and no iOS shader-cache jank like with Flutter. OP likely has a web-dev background and used too many nested views leading to jank (as it would with a native app).
The struggles:
- Inconsistent maintenance of (semi-)official plugins like background uploading and toasts. Hard agree with OP.
- Overuse of outdated, third-party Cocoapods/Gradle plugins for their plugins. Some Cocaopods they use don't even have iCloud support.
- Large backlog of Core issues/bugs
- No more Sidekick (The 'Expo' equivalent for NS), as it wasn't part of the acquisition. This tool was really handy for low-barrier deployments/boilerplate code rollout
But the real problem is adaptation. No large adaptation = no big sponsors = no full-time development. Earlier it was in hands of Progress which had a highly talented team from Bulgaria working on it full-time. Progress tried to use NativeScript as an on-boarding strategy to get people to use Kinvey. When Progress pulled the plug, a small development agency took over development and is struggling to find the manpower to maintain this colossal project. I hope they will manage to make it work as NativeScript does have unique qualities.