slashnull

Nice to see the Haskell community aligning itself so fast around a package manager/build tool created first and foremost for ease of use and convenience.

... okay no I was trolling

Because I think the project should start advocating "PSQL".

See,

The competition is called "MySQL". One syllable, then SQL. You know what it does, and you know how to google it. It googles great, too.

PSQL has the same advantages. Google even already understands it.

Edit: wow, the naming page says that Postgres-QL is a "weird derivation".

wait, what

I can't figure out how it would be possible that shifting from physical paper to online hosting could be more expensive

I see that many OOP languages (of various purity) have interfaces that may be extended by other interfaces. Is that what you're talking about?

I also found that *variance is used in the context of Haskell, but it seems to be far from being widely used.

Haskell being my template of a language with a good-looking interplay of polymorphism and algebraic typing.

The definitive explanation of why inheritance should always be avoided in favour of implementation of abstract interfaces.

Perfect.

Thank you so much.

I think that'd be a fair tradeoff.

The real leap forward here? User interface.

Everywhere I look, I see instances of that same pattern:

One person or small team of very clever people develops a given technique or algorithm, and a gigantic army of technological lumberjacks go out and progressively make it easy to use.

And it's not just UI as in "the paying consumer of a product"; it's UI as in the person which will build the previous UI, and to person which builds that person's tools, and so on, turtles all the way down.

Progress is not algorithms, progress is not ease of use; it's (power of an algorithm / ease of its use).

In the end, progress in user interface is progress, _period_.

It's pretty fascinating that they are willing to solve that problem in such a straightforward and explicit way.

I mean you have Googlers eating, dressing themselves, and even sleeping at Google... What's missing after that, one might ask...

Either way I'm pretty sure the entire phenomenon is just SunnO))) recording albums.

Or for strong and non-mainstream aesthetics.

Depends.

Energy storage efficiency is growing

Homeowners are selling power to their utility during the day and buying it back during the night

People are refraining from buying cars so they can buy flats downtown, and a few good bikes.

DIY-ers with did-it-themselves electric japanese subcompacts are blowing people's mind at drag racing strips

Freeways are being torn down

People are growing food in their backyards

A company with a stated goal of sending people to Mars are landing rockets on barges named after _Culture_ ships

The future is a nice place

That would have been really wild...

     “Not now, Pa, I know the moon’s pretty, I’m right in the middle of debugging this method . . .”

Neat.

I have a nice lil' prototype going on in Snap, I have Persistent running, and I'm this close to have auth working.

But in the meantime, I have lots of logs to parse ; )

...

Halcyon, I'l remember that. I still have to try Nix one day, too

...

Matter of experience, I guess, yeah

...

Precisely, there's a virtuous cycle going around popular platforms due to the larger amounts of features and documentation getting written, and in turn, the larger amount of new devs getting into it. Shame those platforms are built on such bad languages... It's cool to see the web evolving in a direction where Haskell can solve very specific problems without disrupting people's stacks.

- one is dead

- another is the raw Hackage page for a session library spun off from another project

- the last is a cute hello world for the framework that underpins Scotty.

No Node.js tutorial would finish without a working session manager.

Some tutorials will have a few routes and a DB, some other will have an intricate rendering and templating architecture and basically no data storage solution, some are more or less a hello world with a session manager... And there's Yesod, which seems to do everything out of the box, but which has such a colossal amount of dependencies that I never got anything to build beyond fresh yesod-init setups, which still manage to fail on my current setup, despite using Stackage and sandboxes.

Among what I've seen in Haskell, ORMs and web frameworks are the two types of libraries that carry the largest and most cumbersome monad transformer stacks around; making a website involves having to typecheck a huge monad transformer into another huge monad transformer. This is not easy.

Not to mention that, in the world of open-source web developement, nearly all the documentation, expertise, copy-pastable code examples and standard practices are in dynamic OOP languages.

Perhaps the ease of RoR, PHP and Node has let everybody forget how much stuff is involved in making modern webpages : )

After playing with Haskell for the last two years, I figured that it would be pretty damn hard to write conventional LAMP/JS webpages in Haskell, but I still wanted to try to solve some of my real world problems with it.

So I'm parsing the log files that my LAMP stuff produces.

So far it's a very fun and frustrating waste of time, but given my recent progress, it will probably become a slightly less fun and frustrating time saver.

I just recently cleared up some confusion and type errors coming from ByteString/Lazy ByteString/Text/Whatever conversion issues (which made up 95% of the recent frustration, as every other language I'm using right now has one single sort of string (which more than often serves to contain ints ;))

... and database CRUD and JSON typeclass instances have appeared as if by magic.

Awesome!

And now I can celebrate by unleashing that stuff tens of megs of logs, opening top, and then seeing the executable instantly eat up all my RAM, before slowly conceding space to the postgres server.

Hopefully your post will help me implement streaming.

Cheers!