News for hackers. Stuff that matters.
Re:Show HN: A notebook-style Common Lisp environment by oblio on Saturday July 08, 2017 @02:36PM (#14726608)
The Lisp Works page is kind of cute, but in bad way as far as marketing goes, at least in my opinion.

The IDE screenshots for Windows show off Windows XP.

Re:Show HN: A notebook-style Common Lisp environment by pjmlp on Saturday July 08, 2017 @02:47PM (#14726660)
I don't know how the actual UI currently looks like, but even if it still looks like Windows XP, the IDE and Common Lisp compiler are still quite ahead compared with what Emacs + SLIME are capable of, specially in GUI related Lisp development workflows.

Maybe they could improve their marketing message, but I doubt most wannabe Common Lisp developers are willing to pay for comercial tools, with enterprise prices, even if they had the best marketing of all times.

Re:Show HN: A notebook-style Common Lisp environment by xfer on Saturday July 08, 2017 @03:02PM (#14726716)
Also, unless you are heavily invested in CL, most people actually can't afford to pay $600 on a compiler license per year.
Re:Show HN: A notebook-style Common Lisp environment by fiddlerwoaroof on Saturday July 08, 2017 @03:06PM (#14726733)
Lispworks has a free "Personal Edition". It's good enough to get through something like Practical Common Lisp and get a feeling for writing lisp, however since it uses an old version of ASDF, it's a bit difficult to use the "modern" quicklisp ecosystem.
Re:Show HN: A notebook-style Common Lisp environment by lispm on Saturday July 08, 2017 @03:30PM (#14726830)
The LispWorks prices are not per year.
Re:Show HN: A notebook-style Common Lisp environment by ssalazar on Saturday July 08, 2017 @04:52PM (#14727150)
Their pricing pages are also a disaster. I had to drill down a few pages deep to find these epic tables: http://www.lispworks.com/buy/prices-1c.html which presumably could be distilled into 32-bit/64-bit categories plus a maintenance add-on.
Re:Show HN: A notebook-style Common Lisp environment by lispm on Saturday July 08, 2017 @04:30PM (#14727052)
> The IDE screenshots for Windows show off Windows XP.

The IDE is based on their native GUI backend. Thus it picks up much of the looks of the current OS automatically (windows, buttons, dialogs, ...).

Re:Show HN: A notebook-style Common Lisp environment by ssalazar on Saturday July 08, 2017 @04:50PM (#14727144)
The point being made is that they apparently haven't updated their screenshots in over 10 years, making their product seem dated- a pretty big marketing fail.
Re:Show HN: A notebook-style Common Lisp environment by lispm on Saturday July 08, 2017 @05:05PM (#14727195)
LispWorks has been developed from 1987 onwards since 30 years. They can't update their marketing material every year just because someone changed the GUI look. ;-)

Though I'll propose it to them for the next LispWorks release...

Re:Show HN: A notebook-style Common Lisp environment by oblio on Saturday July 08, 2017 @05:22PM (#14727243)
A major Windows release is kind of a big thing in the desktop world.

Missing 5 Windows releases is just sloppy: Vista, 7, 8/8.1, 10.

I'm not saying it's a bad product, just that first impressions matter. There's a reason this site is full of discussions about conversions and funnels.

As a side note, Windows is also 30+ years old. Hardly new tech these days ;)

Re:Show HN: A notebook-style Common Lisp environment by flavio81 on Monday July 10, 2017 @02:18PM (#14738377)
> A major Windows release is kind of a big thing in the desktop world.

I can bet that LispWorks' customers (big companies and experienced lisp users) are largely away from the mainstream desktop world, and wouldn't care too much on how the current Windows UI looks like.

Re:Show HN: A notebook-style Common Lisp environment by ssalazar on Saturday July 08, 2017 @06:08PM (#14727432)
Software age is a non-sequitur- there are plenty of active multi-decade projects that can update their marketing material once in ten years. Nobody suggested they do so every year, even though it takes what like an hour? For a product costing $thousands there is not really an excuse.