ExpiredLink

Java 8

I hope nobody has forged an emissions test.

I will spare us an answer because it wouldn't be printable English.

Many searches that you can easily explain to your grandmother are difficult with regex.

Since accented characters are used in the English language it's not even 'English only'.

IOW, study the implementation to understand the interface.

English only.

>> “This seems to be all profit driven for somebody,” she said, “and I just think it’s a very dangerous process.”

Don't worry! It's just capitalism.

Great resource for critically thinking, informed professionals. Kudos to the author.

Not software decentralization.

>> The solution was to ask buyers and sellers to rate one another and to make those ratings public.

So it isn't trust but social control.

> String processing in computers is difficult.

Not in e.g. Java and many scripting languages.

A string library may mitigate but cannot solve the problem. In C you always need to take allocation/deallocation into consideration.

Don't know why you are voted down, string processing is indeed unpleasantly difficult in C. Partly because a built-in string type would conflict with C's simplistic compile/link schema.

> In what universe did SQL ever go away?

In the blogosphere - admittedly, a rather narrow 'universe'.

You aptly summed it up. The 'stealth mode' is the key to patent success.

What's the use case for this?

>> BMW is now intends to convert all its vehicles to some configuration of plug-in hybrid.

Yep, it's 'just' a "plug-in hybrid". Good for low emissions and high mileage ... on paper.

ncurses isn't supposed to be used on the iPhone anyway ;)

> One of the biggest barriers to understanding others is excessive egocentrism.

A 'Silicon Valley' problem!

>> Work In Sprints

No. A gentleman (developer) walks but never runs.

BTW, if someone wants to professionally connect Mainframes and Internet: http://www.softwareag.com/corporate/products/adabas_natural/...

Any non-trivial application contains dozens, probably even hundreds, of workflows, esp. applications disregarded as CRUD. How do you model workflows for these applications? How do you avoid burying all business logic inextricably in code? How do you keep graphical representations and code in sync over time? Over a long time?

But where is the domain in your Domain Specific Languages? You built SLs but not DSLs.

I'm not over 60 but I'm too old for Scrum. Can anyone over 30 take that Scrum kindergarten serious?

You have no idea.

> When I say DSL I mean external DSL, not a fluent interface.

That's the problem here. 'DSL' is a vague and ambiguous notion. An ad-hoc 'fluent interface' usually isn't considered a DSL.

I never wrote a DSL for a production environment. Once I wrote a DSL that allowed users to script an existing API for testing purposes. In my experience e.g. EDI and ISO specifications and protocols are also good DSLs.

Not only maintaining and growing a DSL is challenging but also designing it at first. You need a lot of both domain and technical experience to achieve a half-decent result. That's why the "hype" around 2007 didn't lead to widespread practice. DSLs are costly.

A classic. Interestingly, RPC-like solutions like SOAP and REST thrive nowadays.