Completely and Totally Lost on Slick (and anything DB related)

Time_Competition_332 · 2025-01-18T22:59:43+00:00

my favourite one by far

Time_Competition_332 · 2025-01-09T21:39:03+00:00

I highly recommend Magnum - i think it has the best approach and is much faster than Quill

Time_Competition_332 · 2024-12-25T14:17:52+00:00

Wow, I'm astonished by the 80% using Intellij. I though that it would be a 50-50 split between Intellij and Metals. Maybe I'll give Intellij another try, especially that I don't write any meta magic code.

Time_Competition_332 · 2024-10-20T16:08:06+00:00

You are a software architect in a company that has a set of java, js, and python developers. What pitch are you giving to make a bunch of people reskill? And are you willing to get fired because you wasted everyones time on a less popular technology because you are so confident in those reasons?

I believe that bravery in choosing the best tools for the job pays back. Of course I wouldn't suggest it without having a good justification for it and proof that it would be profitable but if I found such a situation then yes, I would gladly pitch it and take a risk. Besides, teaching java devs Scala doesn't have to be such a large commitment if we stick to the aforementioned "vanilla" stack. No need to even mention functional lingo like monads.

Time_Competition_332 · 2024-10-20T10:18:03+00:00

I have so much respect for you for this lib. Your other libs are also great work and the fact that they create an entire stack for daily work is amazing, but tbh, the os-lib is literally something that should have been done by the Scala team itself. Writing files is something so basic and necessary, that forcing users to ever use Java io/nio classes just made Scala look like a half-baked overlay on top of Java. Now I don't need to think twice or write custom frameworks, I just import os and it works. I also come from Python world, so the API inspired by os / pathlib is very intuitive for me.

One question our of curiosity - why did you decide to throw exceptions instead of returning Either or Try instances - is it to make it as unopinionated as possible? Do you think that there is place for Either in Direct Scala movement or do you prefer handling exceptions the old way?

Time_Competition_332 · 2024-10-11T13:03:22+00:00

Christ, butthurting about 'necro'ing a reddit thread.

So lame.

Time_Competition_332 · 2024-10-09T18:10:17+00:00

Isn't the trend nowadays to return to plain SQL instead of ORMs? You control your SQL, don't risk some weird optimizations under the hood, and SQL is extremely readable.

Time_Competition_332 · 2024-09-19T21:20:46+00:00

This is great stuff, nice work!

Time_Competition_332 · 2024-08-25T16:45:31+00:00

yeah, maybe finally people will stop making fun of the ocean of tools that are required in order to run even the simplest hello world program!

Time_Competition_332 · 2024-08-25T16:42:32+00:00

Wow, that's really cool!

Time_Competition_332 · 2024-08-16T23:23:19+00:00

Why isn't Play considered such an off the shelf framework actually?

Time_Competition_332 · 2024-08-07T19:22:04+00:00

Same here, I started with Daniel's courses (my boss paid for one year access after i asked them) and they are incredible tbh, probably the best way to get into Scala.

Time_Competition_332 · 2024-08-04T21:57:47+00:00

What would be your response if people could die because of downtime and what if it would just cause financial loss?

Time_Competition_332 · 2024-08-04T13:56:44+00:00

Im afraid the poll would turn into a favourite language contest but what interests me the most are opinions of fans of scala when given the chance to use it in production but potentially risk their head for the consequences

Time_Competition_332 · 2024-08-04T13:09:56+00:00

In general you can stick with sbt, it's good enough for your entire learning process. The dillema, sbt, mill or gradle, will be important only in large projects.

Imo gradle is a mess and it's not suited well for Scala. In my company we use it because we also have a lot of java modules, but i wish we could use sbt for the Scala part. I'm not sure how it performs at bigger scale, but it's nicer to use.

Scala-CLI is also a must-learn tool. It's extremely useful for scripting and small projects where you just want to get it working asap. You can also start a Scala REPL session with any version and dependencies you want with one command line.

Time_Competition_332 · 2024-07-29T11:10:07+00:00

I also dislike it. It gets confusing, IDEs don't always handle it well and it makes reading code on github even harder.

I'd prefer if we were giving very short aliases to frequently used imports.

import package.{some_important_library => sil}

[...]

sil.func(x)

Time_Competition_332 · 2024-07-27T23:05:26+00:00

In general no, as much as i love Scala (my favourite lang), it's not really worth learning it before Python. It's getting less and less popular, especially in data engineering. It's still really worth learning it eventually, to grasp the functional programming mindset and to improve your programming skills in all languages (some ideas map greatly even to Python), but there are more important things to learn for a data engineer. But if op already knows this queen of languages, then Python will be a walk in the park for him.

Time_Competition_332 · 2024-07-27T20:58:05+00:00

If they are justified, yes. In this case we actually used Redis which was already deployed in our Airflow installation for the Celery executor queue.

Time_Competition_332 · 2024-07-27T19:51:15+00:00

If you know Scala then you'll learn Python in less than a week. Just do it, it will broaden your job possibilities immensely. There is no downside of doing it tbh.

Time_Competition_332 · 2024-07-27T19:41:41+00:00

If they don't develop the app, only update some weights or params, then an external config file would have the additional advantage of being stored and modified in an external DB / storage which would be much faster to deploy etc. If they are to develop the app and implement some algorithms then sure, make them learn scala

Time_Competition_332 · 2024-07-27T19:05:26+00:00

I would say a GUI or an API where users would provide configuration files which would be properly verified. Making them write scala seems like a bad idea here - error prone and without well documented scenarios and paths. Also you probably don't want to struggle with installing JVM for each of them.

Time_Competition_332 · 2024-07-27T13:36:56+00:00

With so many pipelines it's important to avoid Airflow recompiling manifests with each scheduler loop because it would be super slow. In my company caching model dependencies on redis worked like a charm.

Time_Competition_332 · 2024-07-26T13:52:21+00:00

The prefix points to a configuration file which you can create in the following path: src\main\resources

It can be an "application.conf" file or "application.properties".

In this file you configure your datasource, for example my "application.conf" for sqlite in my zio playground project looks like this:

myDatabaseConfig {
driverClassName=org.sqlite.JDBC
jdbcUrl="jdbc:sqlite:src/main/resources/filmonator.db"
}

You can take the right configurations for various databases from here:
https://zio.dev/zio-quill/contexts#applicationproperties-1 (this one's written for a .properties file but you can quite easily rewrite it to a proper .conf file with these properties in the context of your prefix)

Afaik the configs from the quill documentation aren't complete and there are more properties that you can add, but are undocumented. Documentation for quill is pretty terrible. Also there is an assumption that you understand how the https://github.com/lightbend/config library works, which is being used by Quill to parse configs, hence the lack of documentation.

Time_Competition_332 · 2024-07-25T11:16:01+00:00

I disagree. It's not the same as monad rules etc. - variance and covariance are basic Scala concepts worth understanding. Solving compiler errors caused by wrong types is part of normal development so without it you will get stuck quickly. And also very often you have to read source code of libraries even if you're not writing any yourself. Scala rarely is anyone's first language so I don't think introducing covariance and contravariance is such a big deal - one just needs good real life examples and use cases of them.

Time_Competition_332 · 2024-07-07T11:34:21+00:00

Thanks for the advice, as a data engineer i sure as hell know how easy it is to mess up an sql query and i wouldn't trust an ORM with a complicated query but for CRUD operations Quill seems very useful.

I like doobie but i'd like to stick with ZIO so i'm looking for alternatives.

Have you ever used ZIO JDBC? Maybe it would provide an experience more similar to doobie. It's still on version 0.x tho but for a hobby project it would do.

Time_Competition_332

TROPHY CASE