Can't help but to mention photopea; https://www.photopea.com/ Pretty impressive stuff made by one guy (it was initially). Basically a viable alternative to photoshop in a browser.
244 karma · joined November 27, 2015
Can't help but to mention photopea; https://www.photopea.com/ Pretty impressive stuff made by one guy (it was initially). Basically a viable alternative to photoshop in a browser.
As an example I've created an alternative to Nissan's Connect EV app. It's basically a way to control and monitor your electric vehicle from Nissan. The official app is I’m very disappointed by; it’s slow and full of wrong decisions.
My alternative is called "My Leaf" and its available on Google Play and the App Store; https://play.google.com/store/apps/details?id=dk.kjeldsen.ca... https://apps.apple.com/us/app/my-leaf-for-nissan-ev/id143670... It's completely open source.
As an example I've created an alternative to Nissan's Connect EV app. It's basically a way to control and monitor your electric vehicle from Nissan. The official app is I’m very disappointed by; it’s slow and full of wrong decisions. My alternative is called "My Leaf" and its available on Google Play and the App Store; https://play.google.com/store/apps/details?id=dk.kjeldsen.ca... https://itunes.apple.com/us/app/my-leaf-for-nissan-ev/id1436...
It's completely open source.
It consists of the main Flutter app and a Dart library for communicating with Nissan's API.
I just love the lightning network. Years of development and it still doesn't work.
I think the Flutter team takes accessibility quite seriously; https://flutter.io/docs/development/accessibility-and-locali...
I've tried Xamarin, React Native and Cordova (god forbids) and native development on iOS and Android. My preference is Flutter.
I've done one big(ish) project with Flutter and it's called "My Leaf" and it is a third party alternative to the NissanConnect EV app. It's used for controlling the Nissan Leaf and Nissan e-NV200 (both EV's). It's open source and available on Android and iOS;
https://play.google.com/store/apps/details?id=dk.kjeldsen.ca...
https://itunes.apple.com/us/app/my-leaf-for-nissan-leaf/id14...
I've seen some of the comments in this post talk about developing plugins for Flutter. I actually think it is easy and does not require much boilerplate contrary to what people say. My guess is that they really haven't tried writing a plugin but only peeked at the documentation.
There are a lot of problems other than double spend with the Bitcoin. Transactions fees rise very quickly because of the block size limit of about 1MB. You can't really rely on 0-confirmation transactions. The saviour lightning network in my opinion is the wrong solution to the scaling problem. It changes fundamentally how bitcoins are exchanged and steers away from the original white paper by Satoshi. Not that this is wrong... it just becomes another project altogether.
I suggest you see this presentation on 1GB blocks (tested on test-net) by Peter Rizun; https://www.youtube.com/watch?v=5SJm2ep3X_M And his talk at "Satoshi's Vision" (here he talks about what is called "weak blocks" and how it can improve scaling and wasted PoW; https://www.youtube.com/watch?v=yXFuNkaYcPQ
It's totally feasible and does not require super computers albeit a Raspberry Pi won't do no more. Scaling to VISA level of transactions is possible. I don't think it's really going to change too much in computing power with bigger blocks. The size of the merkle root won't change just because blocks are larger which means the block header size won't change.
Why do you suspect a second-layer is needed?
Bitcoin Cash, BCH, though is very interesting. It conforms to the original idea (whitepaper) much better in my opnion. No second layer nonsense "solutions". A simple block size limit increase (again) and enablement of Op-Codes (again). All coming 15th of May. The very reason to why Ethereum was created by Vitalik was because Op-Codes usage was too limited on BTC. This changes with BCH; Op-Codes will be back and open for smart contracts. Lots of merchants and people are beginning to use BCH. Because it is fast (0-conf works again) and has close to zero transaction fees. It's the project I began following early 2011.
What big mining operations do is to slice this nonce into appropriate ranges for each miner. So no miner is hashing with the same nonce. So miner 1 starts at nonce=0 and miner 2 on nonce=2000. The nonce range depends on how many hashes each miner can do in a ten minutes span. By doing this each miner is not doing hashing with the same nonce. That would be wasting hashing operations.
Now bitcoin cash changed the difficulty adjustment algorithm (DAA). Instead of adjusting the difficulty every 2016 blocks this is done after each block has been found. This was done to stabilize the difficulty. So miners stay mining bitcoin cash instead of switching between the most profitable chain (bitcoin or bitcoin cash). This was a problem before the new DAA was implemented for bitcoin cash.
There has been times in recent history were no new block was found for 20 minutes on bitcoin. For bitcoin cash around 2 hours. This was in November 2017. It has been 10 minutes stable ever since.
You can check this yourself on bitinfocharts.com for each blockchain under Block Time.
You use what is called the nonce in the block header. Each time you do a hash of the block you increment this nonce. If your hash is under or equal to the difficulty the block is valid. The difficulty essentially means how many zeroes are in front of your hash.
What big mining operations do is to slice this nonce into appropriate ranges for each miner. So no miner is hashing with the same nonce. So miner 1 starts at nonce=0 and miner 2 on nonce=2000. The nonce range depends on how many hashes each miner can do in a ten minutes span. By doing this each miner is not doing hashing with the same nonce. That would be wasting hashing operations.
Now bitcoin cash changed the difficulty adjustment algorithm (DAA). Instead of adjusting the difficulty every 2016 blocks this is done after each block has been found. This was done to stabilize the difficulty. So miners stay mining bitcoin cash instead of switching between the most profitable chain (bitcoin or bitcoin cash). This was a problem before the new DAA was implemented for bitcoin cash.
There has been times in recent history were no new block was found for 20 minutes on bitcoin. For bitcoin cash around 2 hours. This was in November 2017. It has been 10 minutes stable ever since.
You can check this yourself on bitinfocharts.com for each blockchain under Block Time.
No XML or descriptive interface mumbo jumbo. You write your interface purely programmatically and it's easy to read afterwards. It also looks very good and supports most of Material Design's components. Great built-in library. Dart has some very neat features. I especially love the handling of asynchronies operations. Either use promises or the async and await syntax.
It seems like a really big step backwards in big big scheme of things bitcoin. All of the above problems can be solved by increasing the block size. I'm not saying it's the definitive solution... but right now it is a better solution.
A good talk about really big blocks on bitcoin and what the ramifications are; https://www.youtube.com/watch?v=5SJm2ep3X_M