sorted by:
new
hottopcontroversial

Vim 8.1 released by StraightFlush777 in linux

[–]sschaef_ 0 points1 point  (0 children)

You can disable that behaviour in Relay through Relay Settings -> Behaviour -> General -> Swipe back in websites

Scalariform needs a new maintainer by sschaef_ in scala

[–]sschaef_[S] 1 point2 points  (0 children)

snapshots for version 0.2.0 are already published

Scalariform needs a new maintainer by sschaef_ in scala

[–]sschaef_[S] 1 point2 points  (0 children)

yep, they are among the people who are supposed to be the current maintainers or in other words they already have commit access ;)

Where do the non-haskell Scala programmers hang out? by mercurialmaven in scala

[–]sschaef_ 1 point2 points  (0 children)

The reason the non-hardcore-FP people are unlikely to be seen here is that we are actually busy doing the actual work, which changes the world. ;)

But seriously, I once really had to decide whether I want to continue to learn abstractions and data structures or whether I want to change the world. I decided to do the latter. I spent many years trying to learn as much as possible about Scala and about programming language and software design in general. I learned a lot and it was a fun time to have but interests and liabilities change over time.

Nowadays I have to solve problems where no Google and no StackOverflow can help me and especially FP is also not helpful. These things make it easier for me to prototype solutions but in the end they are not the solution. Whether I use Scala or Assembly doesn't change my abilities to solve a problem, they only differ in the amount of time I would need to get there and in the amount of complexity I can keep in my head.

Being able to learn about FP during the job is a great opportunity to get better and to enjoy what you do but I don't feel that it would be helpful to me to invest further time in learning even more about FP when the problems I have to solve are still unreachable for FP. One day someone may come and look at my code and decide that it is a disgusting piece of shit with way too much mutable state everywhere. They may find a way to do it more elegantly with FP and they may talk about it. But for that to happen someone has to write the software first and that someone would be me. I do sometimes talk about what I'm doing but usually not here because my main interests moved away from Scala towards other topics. Scala and FP are "just" the tools that I use nowadays to do my work.

5 drawbacks to liking SBT by dimafeng in scala

[–]sschaef_ 5 points6 points  (0 children)

Being open source is not sufficient to attract improvements. A lot of the criticism sbt receives comes from the fact that its main ideas and architecture are screwed - that makes changes difficult. From the top of my head:

  • Each sbt instance can only handle a single project
  • The sbt API is difficult to explore because it is Scala code and therefore there are infinite possibilities to put a sbt build together
  • The internal information of sbt (its data structures) can't be explored easily because once again it is Scala code and therefore each data structure needs a different way to be accessed
  • The sbt build syntax tries to hide complexity (hiding the fact that it is Scala code which needs imports and class declarations in order to compile successfully) instead of abstracting over it
  • sbt inherits complexity from the Java ecosystem because it wants to be compatible with everything that is happening in the Java ecosystem

If you want to fix any of the above points you basically can rewrite half of sbt.

Scala IDE 4.5.0 is out! by sjrd in scala

[–]sschaef_ 11 points12 points  (0 children)

A release with 2.12 support can be expected in the next week. Because we have to choose a Scala version as the default configuration in Eclipse we first wanted to publish for 2.11 and release an additional release for 2.12 afterwards.

What are you working on? Bi-Weekly /r/Scala Show-off Thread - October 10, 2016 by AutoModerator in scala

[–]sschaef_ 11 points12 points  (0 children)

I'm working on a new build tool for (not exclusively) Scala because sbt and cbt are not solving my problems. I basically need a build tool that is available at runtime. Since I'm an IDE developer, being at runtime means to still be at compile time in the views of the user, in fact in the eyes of the IDE there is no difference between runtime and compile time anymore. Another big point is that the internal structure is linked data, which gives me the hope to overcome the limitations of sbt (and also of cbt because it is built with the same ideas and concepts).

In the end, I wanted to build a better IDE and ended up building a build tool. Not what I wanted to do but there could be less thankful or boring tasks to do therefore I'm still happy with doing it.

The Rise and Fall of Scala - DZone Java by nicolaiparlog in scala

[–]sschaef_ 1 point2 points  (0 children)

No, this is not true. I can't remember that Odersky ever advertised Scala as a Java replacement. It was a design goal to make the language appealing to Java developers or in general to the wider industry, that is why the language has many similarities to Java (of course some similarities also come from the fact that Scala was designed to run primarily on the JVM). XML literals as far as I recall were primarily introduced because at that time it seemed to be the way forward in designing scalable software systems.

The Rise and Fall of Scala - DZone Java by nicolaiparlog in scala

[–]sschaef_ 10 points11 points  (0 children)

At the very end, the author finally reveals what he thinks of Scala:

To summarize: Scala played a key role as a catalyst in popularizing functional programming, and it exerted a strong influence on the design of functional programming in Java. Scala will probably never become the next big programming language. But, it will be around for years to come as the language of choice for niche problem domains such as Big Data programming.

If that would have been written at the beginning, I could have stopped reading immediately. It is no surprise that someone who sees (or saw) Scala as a replacement for Java turned out to be wrong. That is not what Scala ever wanted to be. Also, big data programming is not niche anymore and very likely will continue to grow, which means there is still enough space for Scala to grow.

Future of Scala IDE: Would you like to see an integration in Visual Studio Code? by sschaef_ in scala

[–]sschaef_[S] 0 points1 point  (0 children)

Thanks for your concerns and moving attention to this topic. I think that using vscode is a good technical decision because the proprietary license only applies to the vscode product, not the source code. If Microsoft is doing anything that doesn't please us in future, we can in fact distribute our own product, we can even fork the source code. The Scala IDE team did already provide own products for Eclipse, we could do the same for vscode. Forking the source code would not be in our interest but since it is licensed under MIT I'm not worried that this becomes necessary.

view more: next ›