groundbreaking and thought provoking! 
u mistyped primtive btw.
Ethereum stuck to primitives or assembly.. And a double directed graph would cut down dev costs and ease of use on primitives.. however the million dollar question is: Is there a case you can think of where you would not want to use a graph but use primitives to solve a problem?
I guess vitalik assumes others will build on top if there is a market todo so while we give a leg up on beginners to solve problems quicker but if its a subset of problems then there is a case for primitives or assembly still. That is when will flexibility of primitives be needed in this context where a graph wouldnt work for a layman?
It's also possible that Vitalik simply over looked this. Building something like Ethereum is hard but I think if you're going to build a scripting language you need to make it high level. Right now they have scripting but as a person who can read several programming languages their scripting is awkward and low level.
I think now that they have the resources the Ethereum team should make a scripting language as much like Python or Javascript as possible. You want something which has minimal syntax for people to learn and which is powerful enough to do the job. Python is good as a scripting language because it's powerful but the syntax is very simple.
Serpent is supposed to be like Python and it's getting closer but it's not quite there. I think the competition between Bitshares and Ethereum should be on making it easy to develop for. Whichever DAC is easier to develop for will certainly win over my attention and I would think most people who aren't rock star developers at the same way.
C++ is not the language people will want to mess with when dealing with people's money. Javascript on the other hand is easy and so is Python. If it is easy people will feel confident enough to write code and if projects can be completed in weeks instead of months people will be more likely to make time to do it.
They have serpent and solidity working and full IDEs in development. We will not beat them as a smart contract platform unless we outgrow them first. More likely we will just pull in their VM once both of our systems are more mature.
We are basically all-in on BitAsset adoption and very basic financial services.
If we are all-in on bitassets then shouldn't our priority be to get the protocol stable so we can launch 1.0 and have no further hard forks a for a long time? Only then will we be able to get gateways, our biggest priority.
We already have the killer app, but it's super difficult to get hold of because gateways don't want to integrate with us because our system is still unstable. I think we should have just focused on getting the last UIA changes implemented, and then only focus on UX for the next 6 months for the amazing products we already have. We don't need scripting in the short term, there's not any evidence in the market that it's actually profitable or useful, only hype.
I dont think we should be beginning on working on even more complicated stuff now if it doesn't actually give us any marketing advantage over ethereum. It makes no sense from a business perspective. We need to get our product ready, and then launch it.
I didn't say right now but I'm talking after 1.0. I think 6 months is perhaps a lot longer than you think it is in this hyper competitive environment so I'm worried Bitshares will not be flexible enough to adapt as quickly as Ethereum.
It looks right now like everything will be okay but at the rate things are going anything could happen in 6 months. The plan to go all in on BitAssets in my opinion means everything is going to ride on the marketing team. If the marketing team is successful then Bitshares will become self funding and will be able to hire whatever developers it needs but if not? If marketing fails or if Ethereum wins out on marketing there will be problems.
Right now I'm on the fence. So far Bytemaster and Stan have been wise in their decisions and everything has turned out alright. Things are going to get hyper competitive in 2015 though because either Bitcoin prices will be flat, will go lower, or will go into another epic bubble.
I assume this is one of the final pieces before we have the final 1.0 protocol. Am i right?
Scripting wasn't planned to be implemented in 1.0. This is also just the data structure and wont actually mean that scripting will be functional according to toast. Dont understand why its being put on the testnet but maybe only some of the devs are working on finishing off 1.0 while others are already working on the future updates. I guess that is a good sign meaning that 1.0 will be here relatively soon, probably end of jan.
What i wanted to say was these were the last few changes to the protocol before 1.0
I completely understand the strategy. It's just risky.
I know we need protocol stability so that greater adoption from Gateways can increase the utility of the platform. What I don't know is whether or not the increase in utility will result in an increase in market cap and in transaction volume. It's possible to have the best platform and still people might go to stuff like Ethereum or Counterparty due to politics, or just the charisma of Vitalik and Patrick.
I hope Bitshares is a success though because I have a stake in it.
Topic: Introducing BitShares Object Graph (Read 23267 times)
