145 karma · joined May 4, 2007
It is a double edged sword. The internet serves to amplify the extremes. At least that is the conclusion I draw.
For .com, .net, .org it has historically not been possible to price discriminate like this.
For the "new TLDs" (the explosion of new extensions we have seen in recent years), the registry contract is different and they are indeed allowed to do this. They call it "premium pricing".
Part of the big outcry about the recent changes to .org is that it brings it closer to the "new TLD" model, which disfavors the registrant.
This qualifies you to pay 'wholesale' prices for domain names. Wholesale prices are set by the registry. (e.g. Verisign sets the wholesale price for .com, Afilias for .org, etc.)
It is worth doing if you register a very large number of domain names, like 100,000+. Some large corporations have their own registrar, Google for example. (More recently Google has also entered the registry business, with their new TLDs.)
ICANN -> TLD operator (registry) -> registrar -> reseller (optional) -> registrant (you)
Rather (from Wikipedia):
"Waldorf kindergarten and lower grades generally discourage pupils' use of electronic media such as television and computers.[38] There are a variety of reasons for this: use of these is understood to conflict with young children's developmental needs,[50] media users tend to be physically inactive, and these media often contain inappropriate or undesirable content which may hamper rather than exercise the imagination."
https://en.wikipedia.org/wiki/Waldorf_education#Pre-school_a...
On the other hand, tailgating is always extremely dangerous, even when the speeds involved are relatively low.
"The results suggest that an appropriate altered state of one brain can effect specific predictable frequencies of the electroncephalographic activity of another distant brain which is genetically related."
Contact me by email (in profile) if you'd like to partner in some way.
When code is terrible, it is very difficult to reason about. Hence, you need to be very smart to reason about it, and be successful in modifying it.
I agree. Telerik (and similar) components are great for getting you a lot of functionality straight out of the box, with minimum time and effort.
Where they break down is when you need to make any sort of non-trivial customization or business-specific use case. At that point, it's easier and more maintainable to build things from scratch, or with more loosely coupled base components.
Can someone explain this in layman's terms? Let's say I am a regular programmer / consultant, and I can even hire / manage / scale teams of programmers.
I would be happy to submit a working prototype as part of an RFQ process, in exchange for landing a lucrative and stable government contract.
What exactly is being offered here for someone like me?