PolyglotAPI - Revision history

JaroslavTulach at 08:44, 15 August 2019

JaroslavTulach — Thu, 15 Aug 2019 08:44:17 GMT

←Older revision		Revision as of 08:44, 15 August 2019
Line 3:		Line 3:
	They (mostly) do. However rather than showing how to apply them to each different language one by one, let's try something more advanced. Let's design a single [[PolyglotAPI]] that works for all of them!		They (mostly) do. However rather than showing how to apply them to each different language one by one, let's try something more advanced. Let's design a single [[PolyglotAPI]] that works for all of them!

-	This session will show how to take an existing [[Java]] [[API]] and add [[polyglot]] flavor to it. We show how use that new [[polyglot]] [[API]] from [[JavaScript]], [[Python]], etc. We demonstrate how (surprisingly) fast and efficient such execution can be.	+	This session will show how to take an existing [[Java]] [[API]] and add [[polyglot]] flavor to it. We show how to use that new [[polyglot]] [[API]] from [[JavaScript]], [[Python]], etc. We demonstrate how (surprisingly) fast and efficient such execution can be.

-	If you have your own object oriented database or just pile of ~~bigdata that you want~~ to ~~effectively~~ process by any programming [[language]], stop by. We'll show you how to process such data fast!	+	If you have your own object oriented database or just pile of [[BigData]] to process efficiently by any programming [[language]], stop by. We'll show you how to process such data fast!

JaroslavTulach at 08:41, 15 August 2019

JaroslavTulach — Thu, 15 Aug 2019 08:41:48 GMT

←Older revision		Revision as of 08:41, 15 August 2019
Line 5:		Line 5:
	This session will show how to take an existing [[Java]] [[API]] and add [[polyglot]] flavor to it. We show how use that new [[polyglot]] [[API]] from [[JavaScript]], [[Python]], etc. We demonstrate how (surprisingly) fast and efficient such execution can be.		This session will show how to take an existing [[Java]] [[API]] and add [[polyglot]] flavor to it. We show how use that new [[polyglot]] [[API]] from [[JavaScript]], [[Python]], etc. We demonstrate how (surprisingly) fast and efficient such execution can be.

-	If you have your own object oriented database or just pile of bigdata that you want to effectively process by ~~your languages~~, stop by. We'll show you how to process such data fast!	+	If you have your own object oriented database or just pile of bigdata that you want to effectively process by any programming [[language]], stop by. We'll show you how to process such data fast!

JaroslavTulach at 08:41, 15 August 2019

JaroslavTulach — Thu, 15 Aug 2019 08:41:07 GMT

←Older revision		Revision as of 08:41, 15 August 2019
Line 1:		Line 1:
	The world has changed since [[I]] published the [[TheAPIBook\|Practical API Design]] book. As [[Java]] was the most used programming language at that time it made absolute sense to provide the [[API]] examples in [[Java]]. But since then the world become different. The [[JVM]] ecosystem now supports variety of other languages - be it [[Scala]] or [[Kotlin]]. Moreover a completely new tree of dynamic languages ([[JavaScript]], [[Python]]) has meanwhile flowered into at first sight independent ecosystem of its own. Do the [[API]] design advises still apply?		The world has changed since [[I]] published the [[TheAPIBook\|Practical API Design]] book. As [[Java]] was the most used programming language at that time it made absolute sense to provide the [[API]] examples in [[Java]]. But since then the world become different. The [[JVM]] ecosystem now supports variety of other languages - be it [[Scala]] or [[Kotlin]]. Moreover a completely new tree of dynamic languages ([[JavaScript]], [[Python]]) has meanwhile flowered into at first sight independent ecosystem of its own. Do the [[API]] design advises still apply?

-	They (mostly) do. However rather than showing how to apply them to each different language one by one, let's try ~~sometime~~ more advanced. Let's design a single ~~API~~ that works in all of them!	+	They (mostly) do. However rather than showing how to apply them to each different language one by one, let's try something more advanced. Let's design a single [[PolyglotAPI]] that works for all of them!

	This session will show how to take an existing [[Java]] [[API]] and add [[polyglot]] flavor to it. We show how use that new [[polyglot]] [[API]] from [[JavaScript]], [[Python]], etc. We demonstrate how (surprisingly) fast and efficient such execution can be.		This session will show how to take an existing [[Java]] [[API]] and add [[polyglot]] flavor to it. We show how use that new [[polyglot]] [[API]] from [[JavaScript]], [[Python]], etc. We demonstrate how (surprisingly) fast and efficient such execution can be.

	If you have your own object oriented database or just pile of bigdata that you want to effectively process by your languages, stop by. We'll show you how to process such data fast!		If you have your own object oriented database or just pile of bigdata that you want to effectively process by your languages, stop by. We'll show you how to process such data fast!

JaroslavTulach: New page: The world has changed since I published the Practical API Design book. As Java was the most used programming language at that time it made absolute sense to provide ...

JaroslavTulach — Thu, 15 Aug 2019 08:40:11 GMT

New page: The world has changed since I published the Practical API Design book. As Java was the most used programming language at that time it made absolute sense to provide ...

New page

The world has changed since [[I]] published the [[TheAPIBook|Practical API Design]] book. As [[Java]] was the most used programming language at that time it made absolute sense to provide the [[API]] examples in [[Java]]. But since then the world become different. The [[JVM]] ecosystem now supports variety of other languages - be it [[Scala]] or [[Kotlin]]. Moreover a completely new tree of dynamic languages ([[JavaScript]], [[Python]]) has meanwhile flowered into at first sight independent ecosystem of its own. Do the [[API]] design advises still apply?

They (mostly) do. However rather than showing how to apply them to each different language one by one, let's try sometime more advanced. Let's design a single API that works in all of them!

This session will show how to take an existing [[Java]] [[API]] and add [[polyglot]] flavor to it. We show how use that new [[polyglot]] [[API]] from [[JavaScript]], [[Python]], etc. We demonstrate how (surprisingly) fast and efficient such execution can be.

If you have your own object oriented database or just pile of bigdata that you want to effectively process by your languages, stop by. We'll show you how to process such data fast!